⬆️ Update dependency fluxcd/flux2 to v2.4.0 #17
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/fluxcd-flux2-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v2.3.0
->v2.4.0
Release Notes
fluxcd/flux2 (fluxcd/flux2)
v2.4.0
Compare 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
Bucket
v1 API comes with new features including: proxy support, mTLS and custom STS configuration for AWS S3 and MinIO LDAP authentication.The
GitRepository
v1 API gains support for OIDC authentication. Starting with this version, you can authenticate against Azure DevOps repositories using AKS Workload Identity.The
OCIRepository
v1beta2 API gains support for proxy configuration thus allowing dedicated HTTP/S Proxy authentication on multi-tenant Kubernetes clusters.The
HelmRelease
v2 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.0
v1.30
>= 1.30.0
v1.31
>= 1.31.0
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.
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.proxySecretRef
allows configuring HTTP/S Proxy authentication for the S3-compatible storage service..spec.certSecretRef
allows custom TLS client certificate and CA for secure communication with the S3-compatible storage service..spec.sts
allows 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.provider
allows specifying an OIDC provider used for authentication purposes. Currently, only theazure
provider is supported.OCIRepository v1beta2
The OCIRepository kind gains new optional fields with no breaking changes.
New fields:
.spec.proxySecretRef
allows 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.disableSchemaValidation
allows disabling the JSON schema validation of the Helm release values during installation..spec.upgrade.disableSchemaValidation
allows disabling the JSON schema validation of the Helm release values during upgrade.Upgrade procedure
Upgrade Flux from
v2.3.0
tov2.4.0
either 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/v1
in the YAML files that containBucket
definitions.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 secret
flux create secret proxy
command--proxy-secret-ref
toflux create source
commandsbucket
commands to GA--provider
flag toflux create source git
part-of
label to controllers baseConfiguration
📅 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.
This PR has been generated by Renovate Bot.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.