Flux
v2.8.6CI/CD & App DeliveryFlux v2.8.6 is a patch release fixing helm-controller post-renderer conflicts, a notification-controller regression for generic providers, and adding a MigrateAPIVersion feature gate in kustomize-controller.
breakingAdd 'audience' to GCR Receiver secrets before upgrading to v2.9
The 'audience' field on GCR Receiver secrets is currently optional but will become mandatory in v2.9. Audit your Receiver resources now and add the audience field to any GCR-backed secrets. Doing this proactively prevents a hard failure on your next major upgrade.
breakingGeneric provider commit status events were broken — upgrade immediately if you rely on them
A regression in notification-controller stopped generic providers from forwarding commit status events. If your CI/CD pipelines depend on those webhooks for pipeline gating or observability, they have been silently failing since the prior release. This patch restores that behavior — upgrade to v2.8.6 without delay.
enhancementUse MigrateAPIVersion feature gate when managing resources with deprecated API versions
If kustomize-controller manages resources that use older API versions tracked in managed field entries, the new MigrateAPIVersion feature gate handles migration automatically. Enable it in environments where you're seeing API version drift or drift detection noise from deprecated APIs.
Key changes (5)
- helm-controller: Fixed post-renderer conflict when hooks and templates overlap, and force-replace is now ignored when server-side apply is enabled
- notification-controller: Regression fix restoring commit status forwarding for generic providers — if you use generic webhooks, this one matters
- notification-controller: GCR Receiver secrets now require the 'audience' field; not yet mandatory but will be enforced in v2.9
- kustomize-controller: New MigrateAPIVersion feature gate to handle API version migration in managed field entries
- source-controller and image-automation-controller updated to go-git v5.18.0 for faster Git operations