Repository navigation
chore(deps): update fluxcd/flux2 action to v2.10.0 - #127
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
|
1 similar comment
|
|
drewr
previously approved these changes
Nov 3, 2026
drewr
left a comment
drewr
left a comment
Contributor
There was a problem hiding this comment.
Pinned SHA matches flux2 v2.10.0; CLI-only use in bundle publishing.
renovate
Bot
force-pushed
the
renovate/fluxcd-flux2-2.x
branch
from
November 3, 2026 14:26
7dd67e8 to
a1c1ddd
Compare
renovate
Bot
force-pushed
the
renovate/fluxcd-flux2-2.x
branch
from
November 3, 2026 15:27
a1c1ddd to
c94786a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
v2.7.5→v2.10.0Release Notes
fluxcd/flux2
v2.10.0Compare Source
Highlights
Flux v2.10.0 is a feature release. Users are encouraged to upgrade for the best experience.
Overview of the new features:
ObjectLevelWorkloadIdentityfeature gate is retiredEvent,AlertandProviderAPIs promoted tov1OCIRepositoryas a chart source forHelmRelease--override-manager-before-dry-run(Kustomization).spec.policyChangeDelay, retry on rejected pushes, and.Changed.Summary(ImageUpdateAutomation)ImageRepositorytagsArtifactGenerator)❤️ Big thanks to all the Flux contributors that helped us with this release!
Kubernetes compatibility
This release is compatible with the following Kubernetes versions:
v1.35>= 1.35.2v1.36>= 1.36.1v1.37>= 1.37.0OpenShift compatibility
Flux can be installed on Red Hat OpenShift cluster directly from OperatorHub using Flux Operator. The operator allows the configuration of Flux multi-tenancy lockdown, network policies, persistent storage, sharding, vertical scaling and the synchronization of the cluster state from Git repositories, OCI artifacts, and S3-compatible storage.
Upgrade procedure
createverb on theserviceaccounts/tokenresource. If your installation relies on the default RBAC, bind a ClusterRole with this permission to the controller ServiceAccount before upgrading. See fluxcd/flux2#6139 for the required ClusterRole and ClusterRoleBinding.AlertandProviderAPIs are promoted tov1. Converting av1beta3AlertorProvidertov1drops the deprecatedAlert.spec.summaryandProvider.spec.intervalfields, the static JWT token for Azure Event Hub, and TLS or proxy configuration inProvider.spec.secretRef. UseeventMetadata.summary,proxySecretRefandcertSecretRefinstead.ImageRepositorytag database. Switching the gate wipes the local tag database, so the first reconciliation after the upgrade rescans everyImageRepository. Set--feature-gates=FluxStorage=falseto keep using BadgerDB..spec.kubeConfig.configMapRefuses object identity; replace the legacyaudienceskey withcredential.auth.fluxcd.io/audiences.Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from older versions of Flux to v2.10.
Components changelog
CLI changelog
migrate -fby @matheuscscp in #6020allow-webhooksnetpol to receiver port by @stefanprodan in #6028--app-client-idflag tocreate secret githubappby @Erik-Schuetze in #6090--in-memory-buildrestricting disk access by @rycli in #5974--policy-change-delayto create image update by @stefanprodan in #6146New Contributors
Full Changelog: fluxcd/flux2@v2.9.6...v2.10.0
v2.9.6Compare Source
Highlights
Flux v2.9.6 is a patch release that stops helm-controller from reapplying chart CRDs on every upgrade when server-side apply is enabled, and recovers HelmReleases left with a drifted
Ready=Unknowncondition after a failed status patch. source-controller normalizes Azure Blob listing ETags so unchanged containers are no longer re-downloaded on every reconcile, and evicts stale Helm repository index entries from the cache so repositories with frequently changing indexes no longer fail with "Cache is full". kustomize-controller extends SOPS decryption error redaction tospec.postBuild.substituteFromvalues, so substituted secrets echoed back in API validation errors are masked out of status conditions and events, and adds the opt-inDisableCommitStatusEventfeature gate. Users are encouraged to upgrade for the best experience.ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.
Fixes:
Createpolicy (helm-controller)Ready=Unknowncondition after a failed status patch (helm-controller)NotFoundwhen deleting the HelmChart (helm-controller)spec.postBuild.substituteFromvalues (kustomize-controller)Improvements:
DisableCommitStatusEventfeature gate (kustomize-controller)Components changelog
CLI changelog
Full Changelog: fluxcd/flux2@v2.9.5...v2.9.6
v2.9.5Compare Source
Highlights
Flux v2.9.5 is a patch release that moves helm-controller and source-controller back to upstream Helm, now at v4.2.4, dropping the temporary Flux fork. It hardens the handling of kubeconfig Secrets in helm-controller and kustomize-controller, which now reject kubeconfigs referencing files on the local filesystem and require credentials and certificates to be embedded inline. It also stops kustomize-controller from leaving behind the temporary directories of a previous process that exited without running its cleanup, and fixes a crash in post-build substitution where a substring expression with a negative length, e.g.
${VAR:2:-1}, panicked instead of counting back from the end of the string like Bash does. Across all controllers and the CLI, the fluxcd/pkg dependencies have been updated, bringing Kubernetes to 1.36.4. Users are encouraged to upgrade for the best experience.ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.
Fixes:
.spec.kubeConfigSecrets, rejecting local file references incertificate-authority,tokenFile,client-certificateandclient-key; credentials and certificates must be embedded inline (helm-controller, kustomize-controller)Improvements:
Components changelog
CLI changelog
Full Changelog: fluxcd/flux2@v2.9.4...v2.9.5
v2.9.4Compare Source
Highlights
Flux v2.9.4 is a patch release that ships various fixes to the Flux controllers, covering source-watcher tarball extraction and glob expansion limits, the refspecs accepted by
ImageUpdateAutomation, the HTTP request limits of the notification-controller servers, and Helm repository index loading, OCI chart digest pinning,Bucketerror handling and GCS static authentication in source-controller. On the CLI side,flux migrate -fnow supports migrating repositories to Flux 2.9. Users are encouraged to upgrade for the best experience.Note that this release contains CRD schema changes for
ArtifactGeneratorandImageUpdateAutomation; both CRDs must be updated along with the controllers.ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.
Fixes:
Bucketreconciliation (source-controller)allow-webhooksnetwork policy to the receiver port (flux CLI)Improvements:
flux migrate -f(flux CLI)Components changelog
CLI changelog
migrate -fby @fluxcdbot in #6021allow-webhooksnetpol to receiver port by @fluxcdbot in #6029Full Changelog: fluxcd/flux2@v2.9.3...v2.9.4
v2.9.3Compare Source
Highlights
Flux v2.9.3 is a patch release. It fixes empty lines vanishing from rendered Helm chart manifests, HelmReleases being marked as tested when their Helm test hooks never ran, and
spec.imagesentries that set only some image fields discarding the remaining fields already declared for the same image in thekustomization.yaml. The latter affects both kustomize-controller and theflux build|diff kustomizationcommands. Users are encouraged to upgrade for the best experience.ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.
Fixes:
HasBeenTestedfor all corner cases, where a release could be marked as tested although its Helm test hooks never ran (helm-controller)spec.imagesentry setting only some of the image fields discarding the remaining fields already declared for the same image in thekustomization.yamlatspec.path, e.g. overriding onlynewNameproduced an untagged image reference (kustomize-controller, flux CLI)Improvements:
Components changelog
CLI changelog
Full Changelog: fluxcd/flux2@v2.9.2...v2.9.3
v2.9.2Compare Source
Highlights
Flux v2.9.2 is a patch release. The main fix addresses a regression introduced in
v2.9.1 where a Kustomization with
openapi.pathpointing to a URL failed toreconcile with
failed to read OpenAPI schema. This release also corrects severalCRD field descriptions that contained inaccurate or leaked content. Users are
encouraged to upgrade for the best experience.
ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.
Fixes:
openapi.pathpointing to a URL failed to reconcile withfailed to read OpenAPI schema(kustomize-controller)HelmChartCRD description for.status.url, which pointed users atBucketStatus.Artifactinstead ofHelmChartStatus.Artifact(source-controller)ImageRepositoryCRD description for.status.observedExclusionList, which referred tospec.lastScanResultinstead ofstatus.lastScanResult(image-reflector-controller)ImageUpdateAutomationCRD description for.status.observedSourceRevision, which had a stray Go struct declaration leaking into it (image-automation-controller)Improvements:
Components changelog
CLI changelog
Full Changelog: fluxcd/flux2@v2.9.1...v2.9.2
v2.9.1Compare Source
Highlights
Flux v2.9.1 is a patch release. The main fix, applied across all controllers, disables Flux variable substitution on the Flux CRDs by annotating them with
kustomize.toolkit.fluxcd.io/substitute: disabled, so that Kustomizations with post-build substitution enabled no longer corrupt the CRD schemas when they contain${...}sequences. Users are encouraged to upgrade for the best experience.ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.
Fixes:
${...}sequences (all controllers).inifile decryption (kustomize-controller)<resource> is invalid(kustomize-controller)Improvements:
Components changelog
CLI changelog
Full Changelog: fluxcd/flux2@v2.9.0...v2.9.1
v2.9.0Compare Source
Highlights
Flux v2.9.0 is a feature release. Users are encouraged to upgrade for the best experience.
For a compressive overview of new features and API changes included in this release, please refer to the Announcing Flux 2.9 GA blog post.
Overview of the new features:
flux plugin)Kustomization)Kustomization)Kustomization)HelmRelease)helm --set-literal(HelmRelease)Kustomization,HelmRelease)GitRepository,ImageUpdateAutomation)GitRepository)OCIRepository)ArtifactGenerator)Receiver)❤️ Big thanks to all the Flux contributors that helped us with this release!
Kubernetes compatibility
This release is compatible with the following Kubernetes versions:
v1.34>= 1.34.1v1.35>= 1.35.0v1.36>= 1.36.0OpenShift compatibility
Flux can be installed on Red Hat OpenShift cluster directly from OperatorHub using Flux Operator. The operator allows the configuration of Flux multi-tenancy lockdown, network policies, persistent storage, sharding, vertical scaling and the synchronization of the cluster state from Git repositories, OCI artifacts, and S3-compatible storage.
Upgrade procedure
image.toolkit.fluxcd.io/v1beta2andnotification.toolkit.fluxcd.io/v1beta2have reached end-of-life and have been removed from the CRDs.
Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from older versions of Flux to v2.9.
Components changelog
CLI changelog
--show-sourcetoflux get ksandflux get hrby @rafaelperoco in #5828flux create secret receivercommand by @stefanprodan in #5835--in-memory-buildtoflux build ksandflux diff ksby @rycli in #5794--ignore-not-foundtoflux diff ksby @rycli in #5845flux plugin installby @Iam-Karan-Suresh in #5872--ns-follows-kube-contextglobal flag for using the kubeconfig context namespace by @jtyr in #5831flux trigger receiverby @matheuscscp in #5908Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.