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
The deploy target's `kustomize edit set image` was never actually overriding the base kustomization's image tag. This was masked on non-release branches because the base newTag (latest) happened to
match the hardcoded test image tag. On release branches, the base newTag changes to the release version, exposing the mismatch and causing e2e test pods to stay Pending (image not found in Kind).
Fix by:
- Copying kustomize to .output/ so edits don't modify tracked files
- Matching both short name and registry-prefixed name to ensure the override works regardless of base kustomization state
Extracted from #763.
Signed-off-by: Andy Stoneberg <astonebe@redhat.com>
undeploy: kustomize ## Undeploy controller from the K8s cluster specified in ~/.kube/config. Call with ignore-not-found=true to ignore resource not found errors during deletion.
0 commit comments