Closed brews closed 2 years ago
If this solves the last of these issues with the update, it might be worth dropping an issue with argo-workflows to let them know about the break. At the very least it might help people with the same breaks from applying the newer patches.
Extension of fix from PR #617, PR #618, PR #619.
Applies a similar fix to the
patchesStrategicMerge
for argo-workflow's argo-server ServiceAccount. Apparently, kustomize can't find a unique target to apply the patch to after argo-workflows started hard coding the "argo" namespace in their install.yaml in >= v3.3.5.In case anyone else has the problem, I found this after ArgoCD started reporting errors while syncing:
This pops up after the upstream change from https://github.com/argoproj/argo-workflows/pull/8280. Had no issues with updates and deployments before this change.