-
Notifications
You must be signed in to change notification settings - Fork 810
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
Error: chart requires kubeVersion #3617
Comments
What happens if you run |
Helm command works as expected |
Whatever renders the helm charta believes it renders for k8s 1.26, so maybe that needs to be specified or you need to update that software? Kustomize software version or conff seems reasonable to look deeper at to resolve this. |
Hi there @radhupr 👋! I closed this issue because it was labelled as a support question. Please help us organize discussion by posting this on the https://discourse.jupyter.org/ forum. If it's your first time posting Our goal is to sustain a positive experience for both users and developers. We use GitHub issues for specific discussions related to changing a repository's content, and let the forum be where we can more generally help and inspire each other. Thanks you for being an active member of our community! ❤️ |
I just did a upgrade of kustomize to v5.6.0 and it still the same. Am I the only one facing this then? |
Z2JH just uses standard Helm chart.yaml metadata: If it's not working for you try asking on a Kustomize help forum. |
addressed by kubeVersion parameter in kustomization.yaml |
Thank you for following up for anyone else in the future finding this @radhupr!! |
Bug description
I'm using kustomization.yaml as below
It gives me
Error: chart requires kubeVersion: >=1.28.0-0 which is incompatible with Kubernetes v1.26.0
even though I have the target cluster in version 1.30.0How to reproduce
Run
kustomize build --enable-helm .
command against the file mentioned aboveExpected behaviour
template files created
Actual behaviour
The text was updated successfully, but these errors were encountered: