New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azure v5: change 'None' node pool AZ selection to 'Not specified' #1941
azure v5: change 'None' node pool AZ selection to 'Not specified' #1941
Conversation
|
||
return ( | ||
<RUMActionTarget | ||
name={mergeActionNames(RUMActions.SelectAZSelection, typeName)} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The RUM action name is now computed here, by appending the selection type to the end of the base action name (e.g. SELECT_AZ_SELECTION_AUTOMATIC
)
i would say: "By not specifying the availability zone, Azure will select the zone by itself where the VM size is most available." |
Updated the screenshot 👍🏻 |
src/components/Cluster/ClusterDetail/AddNodePool/AddNodePoolAZSelection.tsx
Outdated
Show resolved
Hide resolved
src/components/Cluster/ClusterDetail/AddNodePool/AddNodePoolAZSelection.tsx
Outdated
Show resolved
Hide resolved
src/components/Cluster/ClusterDetail/AddNodePool/AddNodePoolAZSelection.tsx
Outdated
Show resolved
Hide resolved
LGTM! Gave some input regarding wording. |
Closes https://github.com/giantswarm/giantswarm/issues/13843
In this PR, the
None
NP AZ selection option is changed toNot specified
and a longer explanation is now provided. Also, before, the explanation was shown in a tooltip, which was different from other options. That is now aligned, as well.Unfortunately, to be able to make the option look like the others, it was easier to rewrite the whole AZ selector, than to add the option to the old implementation. In the previous implementation, we were relying on fixed heights, and a lot of CSS class magic. It would've required a lot of hacks to convert the new option and make everything behave correctly on all providers.
In the new implementation, I'm leveraging the
Collapse
component fromreact-bootstrap
. Since we discussed about switching to a UI library, I didn't bother writing custom code for that.The new implementation looks almost 100% the same as the old one, but the transitions are now way quicker, and there are no glitches when switching between
Automatic
andManual
, anymore.Preview