feat(github-release): update flux group to v2.4.0 (minor) #1599
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
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.
This PR contains the following updates:
v2.3.0->v2.4.0v2.3.0->v2.4.0Release Notes
fluxcd/flux2 (fluxcd/flux2)
v2.4.0Compare Source
Highlights
Flux v2.4.0 is a feature release. Users are encouraged to upgrade for the best experience.
For a comprehensive overview of new features and API changes included in this release, please refer to the Announcing Flux 2.4 GA blog post.
This release marks the General Availability (GA) of Flux Bucket API. The
Bucketv1 API comes with new features including: proxy support, mTLS and custom STS configuration for AWS S3 and MinIO LDAP authentication.The
GitRepositoryv1 API gains support for OIDC authentication. Starting with this version, you can authenticate against Azure DevOps repositories using AKS Workload Identity.The
OCIRepositoryv1beta2 API gains support for proxy configuration thus allowing dedicated HTTP/S Proxy authentication on multi-tenant Kubernetes clusters.The
HelmReleasev2 API gains support for disabling JSON schema validation of the Helm release values during installation and upgrade. And allows adopting existing Kubernetes resources during Helm release installation.The Flux controllers are now built with Go 1.23 and their dependencies have been updated to Kubernetes 1.31, Helm 3.16, SOPS 3.9 Cosign 2.4 and Notation 1.2.
❤️ 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.29>= 1.29.0v1.30>= 1.30.0v1.31>= 1.31.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.
API changes
Bucket v1
The Bucket kind was promoted from v1beta2 to v1 (GA).
The v1 API is backwards compatible with v1beta2.
New fields:
.spec.proxySecretRefallows configuring HTTP/S Proxy authentication for the S3-compatible storage service..spec.certSecretRefallows custom TLS client certificate and CA for secure communication with the S3-compatible storage service..spec.stsallows custom STS configuration for AWS S3 and MinIO LDAP authentication.GitRepository v1
The GitRepository kind gains new optional fields with no breaking changes.
New fields:
.spec.providerallows specifying an OIDC provider used for authentication purposes. Currently, only theazureprovider is supported.OCIRepository v1beta2
The OCIRepository kind gains new optional fields with no breaking changes.
New fields:
.spec.proxySecretRefallows configuring HTTP/S Proxy authentication for the container registry service.HelmRelease v2
The HelmRelease kind gains new optional fields with no breaking changes.
New fields:
.spec.install.disableSchemaValidationallows disabling the JSON schema validation of the Helm release values during installation..spec.upgrade.disableSchemaValidationallows disabling the JSON schema validation of the Helm release values during upgrade.Upgrade procedure
Upgrade Flux from
v2.3.0tov2.4.0either by rerunning bootstrap or by using the Flux GitHub Action.To upgrade the APIs, make sure the new CRDs and controllers are deployed, and then change the manifests in Git:
apiVersion: source.toolkit.fluxcd.io/v1in the YAML files that containBucketdefinitions.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
CLI Changelog
flux create secretflux create secret proxycommand--proxy-secret-reftoflux create sourcecommandsbucketcommands to GA--providerflag toflux create source gitpart-oflabel to controllers baseConfiguration
📅 Schedule: Branch creation - "on saturday" (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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.