You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
helm-diff is showing an incomplete diff
... if resources are added via kustomize and the helm chart is local and has dependencies.
helm-diff is behaving correctly
... when not using dependencies and just using a local helm chart with kustomize postRenderer.
Needed resources are provided as code under section resources so it can be reproduced locally.
Versions
# kubectl version with installed kustomize (https://kubectl.docs.kubernetes.io/installation/kustomize/)
Client Version: v1.32.0
Kustomize Version: v5.5.0
# helm version
version.BuildInfo{Version:"v3.16.4", GitCommit:"7877b45b63f95635153b29a42c0c2f4273ec45ca", GitTreeState:"dirty", GoVersion:"go1.23.4"}
# helm diff version
3.9.13
For the sake of this example no complex configuration should be needed as we are just about to throw a diff against a kubernetes cluster and verify if the additional resources come up in the output diff when running helm diff upgrade command as shown under resources/helm-upgrade-command.
Please note that the vpa subchart in goldlocks is set to enabled: false to avoid mis-interpretation.
Actual Result
After running the diff command helmChartAfterKustomize.yaml is showing the VerticalPodAutoscaler that was added to the manifest via vpa-controller.yaml where as in the diff_output.txt or stdout its no where to be found that its to be added.
Expected Result
The diff output should show added resource via postRenderer -> kustomize
Resources
The following instructions under resources should create a directory structure like so
.
├── helm
│ └── Chart.yaml
│ └── values.yaml
├── all.yaml # auto created when helm post-renderer is executed
├── diff_output.txt # auto created when helm diff upgrade is run
├── helmChartAfterKustomize.yaml # auto created when helm post-renderer is executed
├── kustomization.yaml
└── vpa-controller.yaml
---
# for a list of all available attributes see# see https://artifacthub.io/packages/helm/fairwinds-stable/goldilocks?modal=valuesgoldilocks: {}# for a list of all available attributes see# see https://artifacthub.io/packages/helm/oauth2-proxy/oauth2-proxy?modal=valuesproxy-dashboard: {}
Hello,
helm-diff is showing an incomplete diff
... if resources are added via kustomize and the helm chart is local and has dependencies.
helm-diff is behaving correctly
... when not using dependencies and just using a local helm chart with kustomize postRenderer.
Needed resources are provided as code under section resources so it can be reproduced locally.
Versions
For the sake of this example no complex configuration should be needed as we are just about to throw a diff against a kubernetes cluster and verify if the additional resources come up in the output diff when running
helm diff upgrade
command as shown under resources/helm-upgrade-command.Please note that the vpa subchart in goldlocks is set to
enabled: false
to avoid mis-interpretation.Actual Result
After running the diff command
helmChartAfterKustomize.yaml
is showing theVerticalPodAutoscaler
that was added to the manifest viavpa-controller.yaml
where as in thediff_output.txt
or stdout its no where to be found that its to be added.Expected Result
The diff output should show added resource via postRenderer -> kustomize
Resources
The following instructions under resources should create a directory structure like so
helm upgrade command
kustomize.sh
create helm/Chart.yaml
create helm/values.yaml
create values.yaml
kustomization.yaml
vpa-controller.yaml
The text was updated successfully, but these errors were encountered: