Flux Sync status and action are off when namespace is unrelated to flux resource path
When we use the API to configure a Kubernetes Namespace which is unrelated to the Flux Resource Path the "Flux Sync" status and its action break.
For example with the following scenario:
- HelmRelease at
flux-system/gitlab-agent
- HelmRelease
flux-system/gitlab-agent
has a target namespace ofgitlab-agent
- GitLab Environment with:
- Kubernetes Namespace:
gitlab-agent
- Flux Resource Path:
helm.toolkit.fluxcd.io/v2beta1/namespaces/flux-system/helmreleases/gitlab-agent
- Kubernetes Namespace:
The UI gets into a broken state:
To mention is also that this configuration is only possible to set via API and not via UI. The UI as an artificial limitation that couples the kubernetes namespace and the flux resource path. See #498080.
Edited by Timo Furrer