-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
3
-
False
-
None
-
False
-
-
ACM-11816 - Request for advanced configuration option in cluster creation wizard for KubeVirt on ACM console
-
-
-
ACM Console Sprint 263
-
Low
-
None
Value Statement
When deploying HCP clusters on KubeVirt, the user should not be allowed to use the name of the cluster they are creating as a new namespace, or to select any existing namespace that matches the name of an existing ManagedCluster resource.
Definition of Done for Engineering Story Owner (Checklist)
- Hosted cluster namespace dropdown does not show namespaces of managed clusters
- Validation of the Hosted cluster namespace field is enhanced to check that the name is a valid namespace name AND that it does not match an existing managed cluster or the name of the cluster currently being created
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- depends on
-
ACM-9905 No namespace field in kubevirt hcp creation wizard
- Review