Stefan Prodan
Stefan Prodan
Running multiple Flux instances per cluster is not advised. Please see here how to use Flux on multi-tenant clusters: https://github.com/fluxcd/flux2-multi-tenancy
> I saw several cases when one incorrect kustomization (or one incorrect YAML in git repo) broke the whole synchronisation loop. I don't see how this is possible, each Kustomization...
> At first sight this looks like the helm-controller Pod lost access rights on some API resources. Seems that Helm can't list secrets to find the release storage, as if...
@abstractpaper this feels like an EKS bug, kubelet failed to renew the token and Flux ended up using one that has expired. Can you please see the troubleshooting guide here:...
@migspedroso which version of Flux are you using? We fixed the stale token issue for helm-controller in v0.31
@ldemailly good point, I see the Fortio integration as an external service instead of running the CLI inside load tester.
> Then it might be more desirable to leave a app in a failed state instead of rolling it back. For Flagger, rollback means scaling to zero the canary deployment...
> That way it would be guaranteed that once a client hit a new version it will never end up at an older version again. As far as I know,...
I see no need for a `podinfo-dirty` deployment clone. We could allow users to disable the rollback (scale to zero, route all traffic to primary) with a new optional field...
Add `--include-label-prefix=hpa.autoscaling.banzaicloud.io` to Flagger command args and see if it works please.