Michael Vittrup Larsen

True, if you deploy directly from Helm to a Kubernetes cluster, then `GitVersion` may be set even in never Helm. However, there are workflows that apply post processing to the...

I found this - the `extraArgs` field in the kustomize `HelmChartInflationGenerator` are now ignored due to security: https://github.com/kubernetes-sigs/kustomize/pull/3784 This explains the discrepancy between templating the chart with kustomize and helm....

Hi, My observation is that its a bit random if this occurs or not. Another observation is that after observing the issue, if I retry after some minutes the webhook...

An alternative take on rendering Helm charts in declarative pipelines can be found here: https://github.com/michaelvl/krm-functions/blob/main/docs/render-helm-chart.md

Hi, Sorry for the late reply. You can extract edits from a time-range instead of live by using multiple -H arguments like this: ./tracker.py -H '2 hours ago' -H '1...

An option could be to keep the auto-detect based on `.Capabilities.KubeVersion.GitVersion`, but use the existing `cniBinDir` value in the auto-detect: ``` # existing values.yaml defaults: cni: cniBinDir: "" # Auto-detected...

After looking at it a little more, a solution might also be to: 1. Change the cni chart to always simply use `cniBinDir` without any logic 2. Remove the GKE...

The former solution would mean that with tooling where one cannot control `GitVersion` and only `KubeVersion` can be used (and thus the GKE magic does not work), one can still...

@howardjohn yes, you are right. Lets hear if @sergiomcalzada or @matb4r can elaborate on how it broke for them

A test-case that validates the problem can be found here: https://github.com/GoogleContainerTools/kpt/pull/4030