Mario Manno
Mario Manno
An integration test would be helpful, to make sure this stays in place.
Seems related to how helm upgrades services for us. See `https://github.com/kubernetes/kubernetes/issues/105610` fleet-agent should store the error in the bundledeployments status
This was never in a RC
Probably related to https://github.com/rancher/fleet/issues/2551
Cleaning up the backlog.
This can help to identify completed jobs that have not been cleaned up: `kubectl get jobs --all-namespaces -o custom-columns='NAMESPACE:.metadata.namespace,NAME:.metadata.name,OWNER:.metadata.ownerReferences[].name,STATUS:.status.succeeded'`
- [ ] we need to turn https://github.com/rancher/fleet/pull/2907 into a run-once job when #2903 is merged. - [ ] make sure it's actually run when upgrading 0.10.2->0.10.4 - [ ]...
We're looking into the duplicated deploy. However, having a job in a bundle is problematic. Here is an older blog post, that suggests to choose a random name for the...
I added https://github.com/rancher/fleet/issues/2051#issuecomment-2382450978 to the 2.10 milestone, to implement "ignore resources".
We merged a few PRs. Let's verify if this works.