Mario Manno
Mario Manno
The bundle did not deploy any resources? It's only function was to label a namespace? That did work, fleet installed an empty helm chart? We recently excluded fleet.yaml from the...
- [x] re-open PR for custom git server - see [rancher/rancher #43530](https://github.com/rancher/rancher/pull/43530) - [ ] use in a github action to validate PRs
We're waiting for Github Action private runners.
A GitRepo can have multiple bundles, if one of those bundles fails to download its Helm chart, the others should be created. However, in this case it is one bundle...
- [ ] the security context should not be disabled when running e2e tests. can we still enable debug logging, do we want to? - [x] sharding tests should not...
> Wouldn't this validate a `2.9.2` backport ? We created separate backport issues: https://github.com/rancher/fleet/issues/2828
Are you able to capture the status fields of such a stuck GitRepo? https://fleet.rancher.io/troubleshooting#fetch-detailed-status-from-gitrepos-and-bundles
We need to document `FLEET_APPLY_CONFLICT_RETRIES`?
Related to * https://github.com/rancher/fleet/issues/3399 * https://github.com/rancher/fleet/issues/3617
This should be covered by https://github.com/rancher/fleet/issues/3617. Recheck in 2.14