Verify changes in rancher-config for resource requests/limits are applied #4695
Description
In our documentation, we have a section that describes how fleet can be configured for rancher, namely by using a config map named rancher-config. In said config map there's a field fleet which can be used to change fleet configuration (same values as in our fleet.yaml file). Adding this config map file or changing entries in it does not lead the fleet controller's redeployment, for some reason.
It's also been mentioned that configuration of fleet specific features in Rancher is possible using the UI already. It needs to be investigated how those work and if using the rancher-config config map is something that should be possible, or, if there's a different approach that I have not yet been aware of.
My current understanding of how rancher-config works is that some settings like the server-url in Rancher are watched and that changing this setting successfully triggers a redeployment of fleet with the values configured in rancher-config.