-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
3
-
True
-
False
-
None
-
Console Sprint 2023-12
User story:
So that I properly ensure that I have my cluster's node pool configured correctly, as a user I want an easy way to find and apply the proper subnet(s).
Acceptance criteria:
- Search on the subnet drop-downs (Wizard: public, private, and Add Machine Pool) will limit options based on fuzzy (approximate string matching)
- Filtering will not de-select previously selected options.
Mockups:
Mockups | PD 1434
------------------------------------------------------------------------------------
Implementation details:
- depends on
-
HAC-3133 [Hypershift ROSA][Wizard] Create subnet drop-down
- Closed
- is related to
-
HAC-4431 [Hypershift ROSA] Subnet name representation from machine pool step and subnet id representation of same values in "Review and create" step create confusions during final cluster submission.
- Closed
-
HAC-4429 [Hypershift ROSA] Private subnet name shown as "[object object]" wrongly from wizard,
- Closed
-
HAC-4430 [Hypershift ROSA] Change the validation message from "Subnet ID" to "Subnet Name" under machine pool step.
- Closed
-
HAC-4515 [ROSA Hypershift] Change subnet ID references to subnet name from wizard step
- Closed
- relates to
-
HAC-4432 [ROSA Hypershift]Subnet name search seems not filtered result as expected from cluster wizard
- Closed
-
HAC-4743 Refactor fuzzy selection out of aws selection
- Closed
- mentioned on