-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
False
-
-
False
-
-
Description of the problem:
I chose a F05EB00E.D9D7.46B1.BC27.136EB02E22E1 as the name for the workflow. I used the basic workflow software template for this purpose.
How reproducible: 100%
Steps to reproduce:
1. Pick a name using upercase characters (e.g. "F05EB00E.D9D7.46B1.BC27.136EB02E22E1")
2.
3.
Actual results:
Error from server (Invalid): error when creating "F05EB00E.D9D7.46B1.BC27.136EB02E22E1-argocd-app-bootstrap.yaml": Application.argoproj.io "F05EB00E.D9D7.46B1.BC27.136EB02E22E1" is invalid: metadata.name: Invalid value: "F05EB00E.D9D7.46B1.BC27.136EB02E22E1": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Expected results:
The secret is applied w/o problem.
