Skip to content

[Multi_K8s-Plugin] Support per-target kustomizeDir#6718

Open
mohammedfirdouss wants to merge 2 commits intopipe-cd:masterfrom
mohammedfirdouss:feat/multi-target-kustomize-dir
Open

[Multi_K8s-Plugin] Support per-target kustomizeDir#6718
mohammedfirdouss wants to merge 2 commits intopipe-cd:masterfrom
mohammedfirdouss:feat/multi-target-kustomize-dir

Conversation

@mohammedfirdouss
Copy link
Copy Markdown
Contributor

@mohammedfirdouss mohammedfirdouss commented Apr 27, 2026

What this PR does:
Implements support for the kustomizeDir field on KubernetesMultiTarget, which was defined in the config struct and documented in RFC-0014 but never wired up to the manifest loader.

Before this change, the kustomizeDir field was silently ignored and users with multi-target Kustomize overlays in per-cluster subdirectories would never have their kustomization files detected or used.

Why we need it:
Without this fix, any multi-target app relying on per-target Kustomize overlays (e.g. cluster-us/kustomization.yaml) would fall back to plain YAML loading silently, producing incorrect manifests with no error.

Which issue(s) this PR fixes:

Part of #6446

Does this PR introduce a user-facing change?:

  • How are users affected by this change: Multi-target apps with kustomizeDir set per target now correctly detect and run kustomize from that subdirectory instead of the root app directory.
  • Is this breaking change: No
  • How to migrate (if breaking change): N/A

Signed-off-by: Mohammed Firdous <124298708+mohammedfirdouss@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant