-
Bug
-
Resolution: Done
-
Normal
-
4.13.0, 4.14.0
-
Low
-
No
-
Hypershift Sprint 240, Hypershift Sprint 241, Hypershift Sprint 242
-
3
-
False
-
-
-
Bug Fix
-
Done
Description of problem:
hypershift CLI tool allows any string for cluster name. But later when the cluster is to be imported, it needs to confirm to RFC1123. So the user needs to read the error, destroy the cluster and then try again with a proper name. This experience can be improved.
Version-Release number of selected component (if applicable):
4.13.4
How reproducible:
Always
Steps to Reproduce:
1. hypershift create cluster kubevirt --name virt-4.12 ... 2. try to import it
Actual results:
cluster fails to import due to its name
Expected results:
validate the cluster name in the hypershift cli, fail early
Additional info:
- relates to
-
OCPBUGS-17669 Validate Cluster Name in HostedCluster Controller
- Closed
- links to
-
RHEA-2023:5006 rpm