Mario Manno

Ah, yes. We had to vendor those packages, because fleet's go.mod file forces a specific version for k8s libraries and we couldn't bump those with the argo sdk dependency. We...

I always get a modified bundle when I use a setup like this https://github.com/manno/fleet-experiments/tree/diff-experiment1 and edit the service manually. Tested with a fleet-agent 0.3.9, too. However, the config map (https://github.com/manno/fleet-experiments/tree/diff-experiment2)...

The tests worked, if there is an issue it's more specific.

Interesting, the test adds a key to the map, your example changes an existing entry. I can do the same to services, adding another port counts as `nonModified`, changing the...

I tried with 0.3.9 and I see the same behavior: `configmap.v1 test-ns/app-config modified` when changing the value of `.data.app_config.yaml`.

Fleet 0.6.0 (released with Rancher 2.7.2) disables https://github.com/rancher/fleet/pull/1041 for performance.

The documentation applies mostly to fleet standalone, but the Rancher UI also supports some basic multi user GitOps in recent versions: https://fleet.rancher.io/multi-user

This might be related to default values in the [rollout strategy](https://fleet.rancher.io/ref-crds#rolloutstrategy). The defaults are documented in the [fleet.yaml reference](https://fleet.rancher.io/ref-fleet-yaml#reference).

Let's test if this still happens on 2.9.1

When working on this we should - [ ] document how state fields are propagated between resources, like we do for [resource counts](https://fleet.rancher.io/ref-status-fields#resource-counts)