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
When using flux diff kustomization with a local Kustomization yaml, the server diff fails with not found errors when the local kustomization yaml has another resource with the same name.
Steps to reproduce
when i run flux diff kustomization --path <manifests> --kustomize-file <yaml-file>
[Deployment/podinfo namespace not specified: the server could not find the requested resource, HorizontalPodAutoscaler/podinfo namespace not specified: the server could not find the requested resource, Service/podinfo namespace not specified: the server could not find the requested resource, Secret/docker-secret namespace not specified: the server could not find the requested resource, Secret/secret-basic-auth-stringdata namespace not specified: the server could not find the requested resource, Secret/podinfo-token-77t89m9b67 namespace not specified: the server could not find the requested resource, Secret/db-user-pass-bkbd782d2c namespace not specified: the server could not find the requested resource]
Expected behavior
I expect the diff to show me the resources that are changing.
Describe the bug
When using
flux diff kustomization
with a local Kustomization yaml, the server diff fails with not found errors when the local kustomization yaml has another resource with the same name.Steps to reproduce
when i run
flux diff kustomization --path <manifests> --kustomize-file <yaml-file>
with this
<yaml-file>
:i get these failures:
Expected behavior
I expect the diff to show me the resources that are changing.
Screenshots and recordings
No response
OS / Distro
macOS 13.5 (22G74)
Flux version
v2.0.1
Flux check
► checking prerequisites
✔ Kubernetes 1.26.7+k3s1 >=1.24.0-0
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.35.0
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v1.0.0
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v1.0.0
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v1.0.0
► checking crds
✔ alerts.notification.toolkit.fluxcd.io/v1beta2
✔ buckets.source.toolkit.fluxcd.io/v1beta2
✔ gitrepositories.source.toolkit.fluxcd.io/v1
✔ helmcharts.source.toolkit.fluxcd.io/v1beta2
✔ helmreleases.helm.toolkit.fluxcd.io/v2beta1
✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2
✔ kustomizations.kustomize.toolkit.fluxcd.io/v1
✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2
✔ providers.notification.toolkit.fluxcd.io/v1beta2
✔ receivers.notification.toolkit.fluxcd.io/v1
✔ all checks passed
Git provider
No response
Container Registry provider
No response
Additional context
I put a minimal reproduction into a unit test here: #4131
Code of Conduct
The text was updated successfully, but these errors were encountered: