Skip to content
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

nested spire clusterName too long #525

Open
vacan1t opened this issue Feb 10, 2025 · 0 comments
Open

nested spire clusterName too long #525

vacan1t opened this issue Feb 10, 2025 · 0 comments

Comments

@vacan1t
Copy link

vacan1t commented Feb 10, 2025

I am using the spire-nested helmchart and get this error when installing it if I set the clusterName to something longer than 7 characters since prom-cm- is in the template for the port name. I think there is a need to be able to use longer and more describing clusterNames.

Maybe a viable solution would be to use trim here (or maybe there is better place for it:

create Pod spire-external-server-0 in StatefulSet spire-external-server failed error: Pod "spire-external-server-0" is invalid: spec.containers[2].ports[1].name: Invalid value: "prom-cm-makek8ss": must be no more than 15 characters

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant