We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using the latest version, when you try helm install to an EKS cluster, you get an error that looks like this:
helm install
chart requires kubeVersion: >= 1.19.0 which is incompatible with Kubernetes v1.25.13-eks-43840fb
EKS with k8s version 1.25 should be satisfactory.
The reason of the error is explained in this issue: helm/helm#10375
In summary, Helm interprets AWS distro version's -eks postfix as a pre-release version, and fails the version constraint.
-eks
Since AWS won't change it's naming - at least for the existing versions - I think we should implement the workaround in the Chart.yaml file.
No response
The text was updated successfully, but these errors were encountered:
[Helm] Allow pre-release k8s versions to fix AWS EKS deployments (#7183)
de4d4c1
Fixes #7182 by including pre-release versions as explained in the [helm docs](https://helm.sh/docs/chart_template_guide/function_list/#working-with-prerelease-versions).
[Helm] Allow pre-release k8s versions to fix AWS EKS deployments (cva…
335fa2f
…t-ai#7183) Fixes cvat-ai#7182 by including pre-release versions as explained in the [helm docs](https://helm.sh/docs/chart_template_guide/function_list/#working-with-prerelease-versions).
Successfully merging a pull request may close this issue.
Actions before raising this issue
Steps to Reproduce
Using the latest version, when you try
helm install
to an EKS cluster, you get an error that looks like this:Expected Behavior
EKS with k8s version 1.25 should be satisfactory.
Possible Solution
The reason of the error is explained in this issue: helm/helm#10375
In summary, Helm interprets AWS distro version's
-eks
postfix as a pre-release version, and fails the version constraint.Since AWS won't change it's naming - at least for the existing versions - I think we should implement the workaround in the Chart.yaml file.
Context
No response
Environment
No response
The text was updated successfully, but these errors were encountered: