-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enclose label values that are numeric in quotes #1233
Labels
bug
Something isn't working
Comments
akefirad
added
bug
Something isn't working
needs-triage
Priority and effort undetermined yet
labels
May 27, 2023
This issue has not received any attention in 1 year and will be closed soon. If you want to keep it open, please leave a comment below @mentioning a maintainer. |
github-actions
bot
added
the
closing-soon
Issue/PR will be closing soon if no response is provided
label
May 26, 2024
I think this has been fixed. Or at least I don’t see the issue anymore. |
github-actions
bot
removed
the
closing-soon
Issue/PR will be closing soon if no response is provided
label
May 26, 2024
Good news. In any case this is not a cdk8s issue because there is no report of cdk8s malfunctioning here. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug:
I'm not sure if this is a feature or bug, or even what tool needs to take care of it. But it seems the root cause of the issue is deep in Go libraries used in K8S ecosystem. Anyhow, the issue is that even though
123456789
is a perfectly valid value for a label, you cannot deploy the following manifest:Reproduction Steps:
Try to deploy the above manifest.
Error Log:
The attempt fails with different error messages, depending on the tool used to deploy the resource. For example, using
kubectl apply
fails with:ArgoCD fails with:
Environment:
Other:
A quick solution would be to enclose the value in quotes to force it to be string. But would be nice if CDK8S does it automatically.
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: