Mario Manno

> Do we need to add this code to every single fleet.yaml, or is a fix coming in the next update? Yes, this needs to be present in every fleet.yaml...

Is it possible to use https://fleet.rancher.io/gitrepo-add#use-different-helm-credentials-for-each-path We also intend do add globbing to that secret.

> > it also seems that this version broken repos that conatained inlined helm packages, i.e., Chart.yaml, templates, values.yaml files are directly in the repo. It worked before. > >...

This issue now discusses three different bugs: * missing leader election options lead to a panic in the agent: https://github.com/rancher/fleet/pull/3534 * we may have accidentally broken the API. `GitRepo.Status.Resources.PerClusterState` changed...

Was the upgrade done with `--reuse-values`? Normally the environment variables should be set in the fleet-agent deployment. Force redeploying the agent should also work, if the values are updated: https://fleet.rancher.io/troubleshooting#agent-is-no-longer-registered...

Interesting. Are you using [webhooks](https://fleet.rancher.io/webhook) or do you set the `pollingInterval` for git repos? And do you use a ["rolloutStrategy"](https://fleet.rancher.io/next/gitrepo-structure) with partitions? The status of the affected bundle would be...

Let's install a cluster with a about a hundred nodes and try to replicate this.

> Yes, there typically are as the cluster is in a "fluid state". We have made an attempt in trying to remove any failing/modified bundles to make the "cluster green",...

@mirzak In case you're still around for this old issue, can you retry once 2.9.3 (Fleet >=0.10.3) is released?

Cleaning up the backlog, might be fixed in current versions.