Skip to content
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.

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

chore(deps): update dependency fluxcd/flux2 to v2.5.1 #76

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

Conversation

zon-renovate
Copy link
Collaborator

@zon-renovate zon-renovate commented Feb 22, 2025

This PR contains the following updates:

Package Update Change
fluxcd/flux2 minor 2.4.0 -> 2.5.1

Release Notes

fluxcd/flux2 (fluxcd/flux2)

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 - "every weekend" (UTC), 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 has been generated by Renovate Bot.

@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from dd050fe to 916811f Compare February 25, 2025 17:11
@zon-renovate zon-renovate changed the title chore(deps): update dependency fluxcd/flux2 to v2.5.0 chore(deps): update dependency fluxcd/flux2 to v2.5.1 Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant