Skip to content

chore(deps): pin fluxcd/flux2 to v2.7.5 #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): pin fluxcd/flux2 to v2.7.5 #5

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 24, 2023 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
fluxcd/flux2 minor v2.0.1 → v2.7.5

Release Notes

fluxcd/flux2 (fluxcd/flux2)

v2.7.5

Compare Source

Highlights

Flux v2.7.5 is a patch release that comes with fixes to helm-controller. 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:

  • Fix HelmRelease history truncation when using the RetryOnFailure strategy.

⚠️ Note that signature verification for OCI artifacts in source-controller is not compatible with Cosign v3.
Flux users are advised to use Cosign v2.6 for signing Flux OCI artifacts and Helm charts, until support for Cosign v3 is added in Flux v2.8.

Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.7.4...v2.7.5

v2.7.4

Compare Source

Highlights

Flux v2.7.4 is a patch release that comes with various fixes. 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:

  • Add DisableConfigWatchers feature gate to all controllers for disabling the Secrets/ConfigMaps watchers
  • Fix Workload Identity for Azure China Cloud in all controllers
  • Update Helm Go SDK to v3.19.2 fixing schema validation issues in helm-controller
  • Skip secret decryption for remote kustomize patches in kustomize-controller
  • Improve post-build error reporting in kustomize-controller
  • Add ArtifactGenerator to aggregated RBAC roles

⚠️ Note that signature verification for OCI artifacts in source-controller is not compatible with Cosign v3.
Flux users are advised to use Cosign v2.6 for signing Flux OCI artifacts and Helm charts, until support for Cosign v3 is added in Flux v2.8.

Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.7.3...v2.7.4

v2.7.3

Compare Source

Highlights

Flux v2.7.3 is a patch release that comes with various fixes. 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:

  • Restore SOCKS5 proxy support in all controllers
  • Fix status reporting of HelmReleases with RetryOnFailure strategy
  • Automated retries for ImagePolicies when no image tags are found in the database
  • Fix alerting for Telegram's message_thread_id
  • Allow running kustomize-controller and helm-controller on the same loopback interface as source-watcher

⚠️ Note that signature verification for OCI artifacts in source-controller is not compatible with Cosign v3. Users are advised to use Cosign v2.6 for signing Flux OCI artifacts and Helm charts, until support for Cosign v3 is added in Flux v2.8.

Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.7.2...v2.7.3

v2.7.2

Compare Source

Highlights

Flux v2.7.2 is a patch release that comes with security fixes. 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.

All Flux components are now built with Go 1.25.2 which includes fixes for vulnerabilities in the Go stdlib that could lead to denial of service. The list of security fixes can be found in the Go 1.25.2 release notes.

Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.7.1...v2.7.2

v2.7.1

Compare Source

Highlights

Flux v2.7.1 is a patch release that comes with various improvements and fixes. 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.

Improvements:

  • Extend flux migrate with support for migrating manifests in Git repositories to the latest API versions.
  • Add recommendations for configuring HelmReleases on production environments.

Fixes:

  • Fix flux migrate command to handle managed fields properly.
  • Fix self-signed TLS cert handling for public Helm repositories in source-controller.
  • Fix the default API versions used by receivers in notification-controller.
  • Fix redundant Ready condition patching in helm-controller.
  • Fix workload identity configuration examples for kubeconfig in helm-controller and kustomize-controller.
Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.7.0...v2.7.1

v2.7.0

Compare Source

Highlights

Flux v2.7.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.7 GA blog post.

Overview of the new features:

  • General availability release of the Image Automation APIs (ImagePolicy, ImageRepository, ImageUpdateAutomation)
  • Watch for changes in ConfigMaps and Secrets references (Kustomization, HelmRelease)
  • Support for remote cluster authentication using Workload Identity (Kustomization, HelmRelease)
  • Extend the readiness evaluation of dependencies with CEL expressions (Kustomization, HelmRelease)
  • Support for global SOPS Age decryption keys on single-tenant clusters (Kustomization)
  • Support for optional Kustomize components (Kustomization)
  • Introduce RetryOnFailure lifecycle management strategy (HelmRelease)
  • Support mTLS for sending alerts to external systems (Provider)
  • Object-level workload identity authentication (Bucket, Provider)
  • Support mTLS for GitHub App transport (GitRepository, ImageUpdateAutomation, Provider)
  • OpenTelemetry tracing for Kustomization and HelmRelease reconciliation (Provider)
  • Support for 3rd-party source controllers (ExternalArtifact)
  • Support for source composition and decomposition patterns (ArtifactGenerator)
  • CancelHealthCheckOnNewRevision feature gate (kustomize-controller)
  • GitSparseCheckout feature gate (image-automation-controller)

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes version Minimum required
v1.32 >= 1.32.0
v1.33 >= 1.33.0
v1.34 >= 1.34.1

[!NOTE]
Note that the Flux project offers support only for the latest three minor versions of Kubernetes.
Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such as
ControlPlane that provide enterprise support for Flux.

OpenShift 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

⚠️ The Flux APIs v1beta1 and v2beta1 (deprecated in 2023) have reached end-of-life and have been removed from the CRDs.

Unless you are using Flux Operator to deploy the Flux controllers, you must run the flux migrate command on clusters before upgrading.

For more details, please refer to the Flux v2.7 upgrade guide.

Components changelog
New Documentation
CLI changelog
New Contributors

Full Changelog: fluxcd/flux2@v2.6.0...v2.7.0

v2.6.4

Compare Source

Highlights

Flux v2.6.4 is a patch release that comes with various fixes. Users are encouraged to upgrade for the best experience.

Fixes:

  • Fix for SOPS decryption with US Government KMS keys failing with the error:
STS: AssumeRoleWithWebIdentity, https response error\n   StatusCode: 0, RequestID: ,
request send failed, Post\n \"https://sts.arn.amazonaws.com/\": dial tcp:
lookupts.arn.amazonaws.com on 10.100.0.10:53: no such host
Components changelog
CLI changed

Full Changelog: fluxcd/flux2@v2.6.3...v2.6.4

v2.6.3

Compare Source

Highlights

Flux v2.6.3 is a patch release that comes with various fixes. Users are encouraged to upgrade for the best experience.

Fixes:

  • Fix for rsa-sha2-512 and rsa-sha2-256 algorithms not being prioritized for ssh-rsa host keys in source-controller, image-automation-controller and Flux CLI bootstrap.
Components changelog
CLI changed

Full Changelog: fluxcd/flux2@v2.6.2...v2.6.3

v2.6.2

Compare Source

Highlights

Flux v2.6.2 is a patch release that comes with various fixes. Users are encouraged to upgrade for the best experience.

Fixes:

  • Fix authentication for flux push artifact --provider=azure on Azure DevOps runners.
  • Fix OIDC authentication for Amazon ECR Public in source-controller and image-reflector-controller.
  • Fix knownhosts key mismatch regression bug in the Flux CLI, source-controller and image-automation-controller.
Components changelog
CLI changelog

Full Changelog: fluxcd/flux2@v2.6.1...v2.6.2

v2.6.1

Compare Source

Highlights

Flux v2.6.1 is a patch release that comes with various fixes. Users are encouraged to upgrade for the best experience.

Fixes:

  • Fix a bug introduced in image-reflector-controller v0.35.0 that was causing spurious error events for policies during image repository reconciliation.
  • Fix excessive logging in image-reflector-controller after a restart when the image tags cache is empty.
Components changelog
  • image-reflector-controller v0.35.1
CLI changelog

Full Changelog: fluxcd/flux2@v2.6.0...v2.6.1

v2.6.0

Compare Source

Highlights

Flux v2.6.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.6 GA blog post.

Overview of the new features:

  • General availability release for the Flux OCI Artifacts APIs and flux artifact commands
  • Support for OCI digests pinning (ImagePolicy, ImageUpdateAutomation)
  • Object-level workload identity authentication (OCIRepository, ImageRepository, Kustomization, Alert Provider)
  • Cache registry credentials for cloud providers (OCIRepository, ImageRepository)
  • Git HTTP/S Mutual TLS authentication (GitRepository, ImageUpdateAutomation)
  • Support for sparse checkout (GitRepository)
  • Support for GitHub App authentication (Alert Provider)
  • Support for managed Identity authentication to Azure Event Hub (Alert Provider)
  • Customize the ID of the Git commit status with CEL expressions (Alert Provider)
  • WaitForTermination deletion policy (Kustomization)
  • DisableChartDigestTracking feature gate (HelmRelease)

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes version Minimum required
v1.31 >= 1.31.0
v1.32 >= 1.32.0
v1.33 >= 1.33.0

[!NOTE]
Note that the Flux project offers support only for the latest three minor versions of Kubernetes.
Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such as
ControlPlane that provide enterprise support for Flux.

OpenShift 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

Upgrade Flux from v2.5.0 to v2.6.0 by following the upgrade guide.

To upgrade the APIs, make sure the new CRDs and controllers are deployed, and then change the manifests in Git:

  1. Set apiVersion: source.toolkit.fluxcd.io/v1 in the YAML files that contain OCIRepository definitions.
  2. Add an annotation api.fluxcd.io/upgrade: "v2.6.0" to the OCIRepository resources. (this is not required if Flux Operator is used for upgrade)
  3. Commit, push, and reconcile the API version changes.

Bumping the APIs version in manifests can be done gradually.
It is advised to not delay this procedure as the deprecated versions will be removed after 6 months.

Components changelog
New Documentation
What's Changed
New Contributors

Full Changelog: fluxcd/flux2@v2.5.0...v2.6.0

v2.5.1

Compare Source

Highlights

Flux v2.5.1 is a patch release which comes with various fixes. Users are encouraged to upgrade for the best experience.

Fixes:

  • Fix a bug introduced in kustomize-controller v1.5.0 that was causing spurious logging for deprecated API versions and health check failures.
  • Sanitize the kustomize-controller logs when encountering errors during SOPS decryption.
Components changelog
CLI Changelog

v2.5.0

Compare Source

Highlights

Flux v2.5.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.5 GA blog post.

Overview of the new features:

  • Support for GitHub App authentication (GitRepository and ImageUpdateAutomation API)
  • Custom Health Checks using CEL (Kustomization API)
  • Fine-grained control of garbage collection (Kustomization API)
  • Enable decryption of secrets generated by Kustomize components (Kustomization API)
  • Support for custom event metadata from annotations (Alert API)
  • Git commit status updates for Flux Kustomizations with OCIRepository sources (Alert API)
  • Resource filtering using CEL for webhook receivers (Receiver API)
  • Debug commands for Flux Kustomizations and HelmReleases (Flux CLI)

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes version Minimum required
v1.30 >= 1.30.0
v1.31 >= 1.31.0
v1.32 >= 1.32.0

[!NOTE]
Note that the Flux project offers support only for the latest three minor versions of Kubernetes.
Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such as
ControlPlane that provide enterprise support for Flux.

OpenShift 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

Upgrade Flux from v2.4.0 to v2.5.0 by following the upgrade guide.

There are no new API versions in this release, so no changes are required in the YAML manifests containing Flux resources.

Components changelog
CLI Changelog

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.1.0 chore(deps): pin fluxcd/flux2 to v2.1.1 Sep 19, 2023
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 55193a1 to 365f033 Compare September 19, 2023 13:31
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.1.1 chore(deps): pin fluxcd/flux2 to v2.1.2 Oct 12, 2023
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 365f033 to 16aa0da Compare October 12, 2023 13:59
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 16aa0da to 45e20bb Compare December 12, 2023 16:31
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.1.2 chore(deps): pin fluxcd/flux2 to v2.2.0 Dec 12, 2023
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 45e20bb to 5815c39 Compare December 16, 2023 04:56
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.2.0 chore(deps): pin fluxcd/flux2 to v2.2.1 Dec 16, 2023
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 5815c39 to 2f1fb5f Compare December 19, 2023 18:31
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.2.1 chore(deps): pin fluxcd/flux2 to v2.2.2 Dec 19, 2023
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 2f1fb5f to 8880499 Compare February 5, 2024 15:38
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.2.2 chore(deps): pin fluxcd/flux2 to v2.2.3 Feb 5, 2024
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 8880499 to 469139e Compare May 13, 2024 14:32
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.2.3 chore(deps): pin fluxcd/flux2 to v2.3.0 May 13, 2024
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 469139e to ccf3ecf Compare September 30, 2024 18:54
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.3.0 chore(deps): pin fluxcd/flux2 to v2.4.0 Sep 30, 2024
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from ccf3ecf to db7dede Compare February 20, 2025 15:47
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.4.0 chore(deps): pin fluxcd/flux2 to v2.5.0 Feb 20, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from db7dede to b279dc4 Compare February 25, 2025 19:47
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.5.0 chore(deps): pin fluxcd/flux2 to v2.5.1 Feb 25, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from b279dc4 to e97b521 Compare May 29, 2025 14:45
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.5.1 chore(deps): pin fluxcd/flux2 to v2.6.0 May 29, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from e97b521 to b090351 Compare June 5, 2025 21:41
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.6.0 chore(deps): pin fluxcd/flux2 to v2.6.1 Jun 5, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from b090351 to 75132dc Compare June 16, 2025 16:14
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.6.1 chore(deps): pin fluxcd/flux2 to v2.6.2 Jun 16, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 75132dc to 441f59b Compare June 27, 2025 11:48
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.6.2 chore(deps): pin fluxcd/flux2 to v2.6.3 Jun 27, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 441f59b to 47e1213 Compare July 8, 2025 11:56
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.6.3 chore(deps): pin fluxcd/flux2 to v2.6.4 Jul 8, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 47e1213 to 859860a Compare September 30, 2025 09:39
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.6.4 chore(deps): pin fluxcd/flux2 to v2.7.0 Sep 30, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 859860a to 393389d Compare October 6, 2025 18:42
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.7.0 chore(deps): pin fluxcd/flux2 to v2.7.1 Oct 6, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 393389d to df10650 Compare October 8, 2025 20:36
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.7.1 chore(deps): pin fluxcd/flux2 to v2.7.2 Oct 8, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from df10650 to 32c69bb Compare October 28, 2025 19:14
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.7.2 chore(deps): pin fluxcd/flux2 to v2.7.3 Oct 28, 2025
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from 32c69bb to f0882ea Compare November 24, 2025 17:54
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.7.3 chore(deps): pin fluxcd/flux2 to v2.7.4 Nov 24, 2025
@renovate
chore(deps): pin fluxcd/flux2 to v2.7.5
095fb2b 
| datasource      | package      | from   | to     |
| --------------- | ------------ | ------ | ------ |
| github-releases | fluxcd/flux2 | v2.0.1 | v2.7.5 |
@renovate renovate bot force-pushed the chore/renovate/fluxcd-flux2-2.x branch from f0882ea to 095fb2b Compare November 27, 2025 15:07
@renovate renovate bot changed the title chore(deps): pin fluxcd/flux2 to v2.7.4 chore(deps): pin fluxcd/flux2 to v2.7.5 Nov 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant