-
Bug
-
Resolution: Done
-
Blocker
-
None
-
False
-
None
-
False
-
-
-
No
Summary of the issue:
When OCM creates the ID for the cluster, if it starts with a number, addon-cluster-proxy-deploy-0 fails to be deployed:
What triage steps have been taken so far?:
For example, for clusterID: 20pi8725abdjf5lccjlt61dnqidp1bm2
On the management cluster:
Namespace: klusterlet-20pi8725abdjf5lccjlt61dnqidp1bm2
POD: klusterlet-20pi8725abdjf5lccjlt61dnqidp1bm2-work-agent-b99rw94f
E1223 09:27:20.700245 1 base_controller.go:270] "ManifestWorkAgent" controller failed to sync "addon-cluster-proxy-deploy-0", err: Service "20pi8725abdjf5lccjlt61dnqidp1bm2" is invalid: metadata.name: Invalid value: "20pi8725abdjf5lccjlt61dnqidp1bm2": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name', or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?')
Region: us-east-2
Management Cluster: hs-mc-mdqo7k4u0
This makes cluster installation never ends