deploy.sh requires standalone kustomize binary

[ktdreyer]

Jira: RHOAIENG-51905

Problem

components/manifests/deploy.sh requires a standalone kustomize binary. It checks for it with command_exists kustomize and calls it directly throughout the script (kustomize build, kustomize edit set image, kustomize edit set namespace, etc.).

This is unnecessary because kubectl already ships with kubectl kustomize built in, and kubectl is already a prerequisite for this script.

Proposal

Replace all kustomize calls with kubectl kustomize and remove the standalone binary check.

Note: the e2e deploy script (e2e/scripts/deploy.sh) already uses kubectl kustomize and does not have this problem.

(Written by Claude Code / Opus 4.6)

[github-actions]

Inactive for 30 days. Will close in 7 days unless there's activity.

[ktdreyer]

Update: kustomize edit is not available via kubectl

Research shows that kubectl kustomize only integrates the build functionality from standalone kustomize — the edit subcommand was intentionally excluded from kubectl (KEP discussion, PR #73033).

This script uses both kustomize build and kustomize edit set image/kustomize edit set namespace. Replacing kustomize build with kubectl kustomize is straightforward, but we would need to choose a solution for the edit calls:

• Replace with sed
• Evaluate each edit call to see if we could simplify it to use fully-declarative configurations

[jeremyeder]

Housekeeping: reviewing open issues. @ktdreyer is this still relevant / something you plan to work on? If not, we'll close it out. No pressure either way — just trimming the backlog.

[jeremyeder]

Hey there! 👋 Closing this out as part of a triage pass — it's been idle for a while and we want to keep the backlog focused. If this is still relevant or you'd like to pick it back up, feel free to reopen anytime. Thanks!