Release v0.3.6 · rancher/fleet

Enhancements

Add image scanning functionality #378
Add Rancher Webhook integration #424
Add valuesFrom feature for ConfigMaps and Secrets to provide values.yaml for Fleet #384
Bump core libraries and images for bug fixes and security enhancements (e.g. Kubernetes libraries to v1.21.3) #505
Clean up leftover registration objects on cluster delete #478
Deploy new fleet-agent if agentEnvVars have changed based on cluster status #34368
Ensure Fleet works on Kubernetes v1.22 clusters #33112
Support bundle dependency #392

Fix array usage in Helm values provided by cluster labels #363
Fix fleet-controller functionality in hardened clusters #130 / #32825
Fix the old fleet-agent being stuck in an uninstalling state upon upgrade #362
Fix an issue where fleet-controller does not work properly in proxy environments with Rancher #34511
Fix an issue where Fleet will fail to deploy Helm charts with CRD folder #458
Fix an issue where Fleet fails to use a ServiceAccount to deploy Fleet bundles due to mis-configured prefix name #372
Miscellaneous fixes for Rancher's Provisioning v2 tech preview, which includes mitigating edge cases and fixing performance inconsistencies that may be encountered in standalone Fleet as well as Fleet in Rancher

Update default namespace fleet-system to cattle-fleet-system to avoid collisions with other apps named "fleet" (side note: automatic migration will occur upon upgrade) #395
Rancher v2.6's new cluster provisioning system leverages Fleet's bundle deployment capabilities in order to manage clusters at scale. Therefore, in Rancher v2.6, Fleet can no longer be disabled. If Fleet was disabled in Rancher v2.5.x, it will become enabled if Rancher is upgraded to v2.6.x. A new feature flag was added to Rancher to disable the GitOps CD portion for end users within Rancher #31044 / #32688 / #32808

A DEVELOPING.md file has been added for local development with Fleet (and for Fleet in Rancher) #482 / #506