Jonathan West
Jonathan West
FYI @shubhamagarwal19
Merging as no objections were raised.
/ok-to-test
Confirmed, I see this on DigitalOcean K8s as well, and is likely a case where Cilium and Argo CD have incompatible behaviours. By default, Argo CD uses `app.kubernetes.io/instance` label to...
Cluster configuration is handled by Argo CD, see https://argo-cd.readthedocs.io/en/stable/getting_started/#5-register-a-cluster-to-deploy-apps-to-optional and/or https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#clusters A cluster must first be defined (and working) within Argo CD, before ApplicationSet controller can use it.
When I run `make test` on master branch, the tests pass without any issue, so the test failures are likely due to changes on this PR.