Update dependency fluxcd/flux2 to v2.4.0 #18
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/all"
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.2.1
->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 compressive 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 basev2.3.0
Compare Source
Highlights
Flux v2.3.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.3 GA blog post.
This release marks the General Availability (GA) of Flux Helm features and APIs, including helm-controller, the
HelmRelease
,HelmChart
, andHelmRepository
APIs.The
HelmRepository
v2 API comes with new features, such as the ability to reference Helm charts fromOCIRepository
sources, reuse existingHelmChart
resources, and verify the integrity of Helm chart artifacts signed with Notary Notation.❤️ 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.28
>= 1.28.0
v1.29
>= 1.29.0
v1.30
>= 1.30.0
API changes
HelmRelease v2
The HelmRelease kind was promoted from v2beta2 to v2 (GA).
The v2 API is backwards compatible with v2beta2, with the exception of the deprecated fields which have been removed.
Removed fields:
.spec.chart.spec.valuesFile
replaced by.spec.chart.spec.valuesFiles
..spec.postRenderers.kustomize.patchesJson6902
replaced by.spec.postRenderers.kustomize.patches
..spec.postRenderers.kustomize.patchesStrategicMerge
replaced by.spec.postRenderers.kustomize.patches
..status.lastAppliedRevision
replaced by.status.history.chartVersion
.New fields:
.spec.chartRef
allows referencing chart artifacts fromOCIRepository
andHelmChart
objects..spec.chart.spec.ignoreMissingValuesFiles
allows ignoring missing values files instead of failing to reconcile.HelmChart v1
The HelmChart kind was promoted from v1beta2 to v1 (GA).
The v1 API is backwards compatible with v1beta2, with the exception of the deprecated fields which have been removed.
Removed fields:
.spec.valuesFile
replaced by.spec.chart.valuesFiles
.New fields:
.spec.ignoreMissingValuesFiles
allows ignoring missing values files instead of failing to reconcile..spec.verify.provider: notation
verify the signature of a Helm OCI artifacts using Notation trust policy and CA certificate.HelmRepository v1
The HelmRepository kind was promoted from v1beta2 to v1 (GA).
The v1 API is backwards compatible with v1beta2.
OCIRepository v1beta2
The OCIRepository kind gains new optional fields with no breaking changes.
New fields:
.spec.ref.semverFilter
allows filtering the tags based on regular expressions before applying the semver range..spec.verify.provider: notation
verify the signature of OCI artifacts using Notation trust policy and CA certificate.Kustomization v1
The Flux Kustomization kind gains new optional fields with no breaking changes.
New fields:
.spec.namePrefix
allows setting a name prefix for the generated resources..spec.nameSuffix
allows setting a name suffix for the generated resources.ImageUpdateAutomation v1beta2
The ImageUpdateAutomation kind was promoted from v1beta1 to v1beta2.
The v1beta2 API is backwards compatible with v1beta1.
Deprecated fields:
Updated
template data has been deprecated in favour ofChanged
that is designed to accommodate for all the types of updates made.New fields:
.spec.policySelector
allows filteringImagePolicy
based on labels.Receiver v1
The Receiver kind gains new optional fields with no breaking changes.
New fields:
.spec.type: cdevents
allows receiving, validating and filtering of CDEvents.Upgrade procedure
Upgrade Flux from
v2.x
tov2.3.0
either by rerunning bootstrap or by using the Flux GitHub Action.For more details, please refer to the upgrade guide from the Announcing Flux 2.3 GA blog post.
Components changelog
New Documentation
CLI Changelog
HelmRelease
API to v2 (GA)(create|delete|export) source chart
commands--reproducible
flag toflux push artifact
flux reconcile
andflux create
--ssh-hostkey-algos
flag to bootstrap commandGOMAXPROCS
andGOMEMLIMIT
to all Flux controllersflux envsubst
command--strict-substitute
flag toflux build ks
andflux diff ks
--registry-creds
flag to bootstrap and install commandsImageUpdateAutomation
API to v1beta2--force
flag descriptionflux check
should error on unrecognised argsflux stats
should error on unrecognised argsv2.2.3
Compare Source
Highlights
Flux v2.2.3 is a patch release which comes with various fixes and improvements. Users are encouraged to upgrade for the best experience.
💡 For upgrading to Flux v2.2, please see the procedure documented in 2.2.0.
This release updates the Kubernetes dependencies to v1.28.6 and various other dependencies to their latest version to patch upstream CVEs.
All controllers are built with Go 1.21.6 using Alpine Linux 3.19.1 base image.
Fixes:
Roles
andClusterRoles
with aggregated roles were continuous reconciled by kustomize-controller has been fixed.See the components changelog for a full list of bug fixes.
Components changelog
CLI Changelog
flux check
should error on unrecognised argsflux stats
should error on unrecognised argsv2.2.2
Compare Source
Highlights
Flux v2.2.2 is a patch release that addresses an issue with the label selector sharding functionality in the helm-controller. Users are encouraged to upgrade for the best experience.
💡 For upgrading to Flux v2.2, please see the procedure documented in 2.2.0.
Components changelog
CLI Changelog
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
Update dependency fluxcd/flux2 to v2.2.2to Update dependency fluxcd/flux2 to v2.2.3dbe615d4ec
to80a0591ba8
Update dependency fluxcd/flux2 to v2.2.3to Update dependency fluxcd/flux2 to v2.3.080a0591ba8
to2dca436966
Update dependency fluxcd/flux2 to v2.3.0to Update dependency fluxcd/flux2 to v2.4.02dca436966
to730269f97a