-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Helm chart dynamic version detection not working #6466
Comments
@Gby56, I did some research, looks like it is not the bug in our Helm, this is problem that EKS (AWS) is not respecting the semVer standard of versioning. I will rethink and maybe implement kind of workaround. |
I'm having the same issue with microk8s, it's probably not specific to EKS.
That being said, the deprecation note: https://github.com/helm/helm/blob/72e2bff0aff44734056be2c859921f2cb22bb2f9/pkg/chartutil/capabilities.go#L82 A better solution would be to use |
@metcox good point, I will adjust helm. |
@Gby56 and @metcox can you please test https://github.com/dsever/django-DefectDojo/tree/helmv3_check_capabilities I don't have AWS or microk8s |
@dsever it's working well with microk8s , thanks |
Bug description
I'm currently trying to redeploy DDojo 2.10.0 on an EKS cluster 1.22 v1.22.9-eks-a64ea69
I've been having lots of issues relating to Ingress definitions, I managed to correct a lot of them by tweaking the chart, but I think the
semverCompare
is not working as intended in the chart. (maybe because the EKS versioning is weird ?)First error I was getting:
which clearly showed that the version detected was not correct imo ? I have changed the apiVersion in django-ingress.yaml to
networking.k8s.io/v1
in both conditions of the{{- if semverCompare ">=1.19.0" .Capabilities.KubeVersion.GitVersion }}
Then I had a few more issues
Steps to reproduce
Steps to reproduce the behavior:
Try to deploy it on an EKS cluster ? maybe you could reproduce the issue if you could change the version returned by
kubectl version
or at least test the semverCompare, I think there are issues like this in other projects... kubernetes/ingress-nginx#8271my kubectl version:
Server Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.9-eks-a64ea69", GitCommit:"540410f9a2e24b7a2a870ebfacb3212744b5f878", GitTreeState:"clean", BuildDate:"2022-05-12T19:15:31Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}
Deployment method (select with an
X
)Environment information
The text was updated successfully, but these errors were encountered: