chore(deps): update dependency fluxcd/flux2 to v2.7.0 #304
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.4.0
->v2.7.0
Release Notes
fluxcd/flux2 (fluxcd/flux2)
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:
ImagePolicy
,ImageRepository
,ImageUpdateAutomation
)Kustomization
,HelmRelease
)Kustomization
,HelmRelease
)Kustomization
,HelmRelease
)Kustomization
)Kustomization
)RetryOnFailure
lifecycle management strategy (HelmRelease
)Provider
)Bucket
,Provider
)GitRepository
,ImageUpdateAutomation
,Provider
)Kustomization
andHelmRelease
reconciliation (Provider
)ExternalArtifact
)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:
v1.32
>= 1.32.0
v1.33
>= 1.33.0
v1.34
>= 1.34.1
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
v1beta1
andv2beta1
(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
v2.6.x
by @stefanprodan in https://github.com/fluxcd/flux2/pull/5379flux push artifact --provider azure
on DevOps runners by @matheuscscp in https://github.com/fluxcd/flux2/pull/5390knownhosts key mismatch
regression bug by @matheuscscp in https://github.com/fluxcd/flux2/pull/5404normalize.UnstructuredList
instead ofssa.SetNativeKindsDefaults
by @cappyzawa in https://github.com/fluxcd/flux2/pull/5407flux create tenant
by @reiSh6phoo9o in https://github.com/fluxcd/flux2/pull/5402flux push artifact
for insecure registries by @stefanprodan in https://github.com/fluxcd/flux2/pull/5449flux diff kustomization
ignore patterns by @dgunzy in https://github.com/fluxcd/flux2/pull/5451app.kubernetes.io/part-of: flux
label to controller pods by @pinkavaj in https://github.com/fluxcd/flux2/pull/5440flux migrate
command by @stefanprodan in https://github.com/fluxcd/flux2/pull/5473GOMAXPROCS
by @stefanprodan in https://github.com/fluxcd/flux2/pull/5501--all-namespaces
flag by @mohiuddin-khan-shiam in https://github.com/fluxcd/flux2/pull/5414--show-history
flag todebug helmrelease
by @hawkaii in https://github.com/fluxcd/flux2/pull/5505ArtifactGenerator
kind by @stefanprodan in https://github.com/fluxcd/flux2/pull/5520flux [reconcile|suspend|resume] image policy
commands by @lukas8219 in https://github.com/fluxcd/flux2/pull/5492force: enabled
annotation influx diff ks
command by @stefanprodan in https://github.com/fluxcd/flux2/pull/5528fluxcd/gha-workflows
by @stefanprodan in https://github.com/fluxcd/flux2/pull/5529ArtifactGenerators
during uninstall by @stefanprodan in https://github.com/fluxcd/flux2/pull/5531ExternalArtifact
toflux trace
by @stefanprodan in https://github.com/fluxcd/flux2/pull/5532--show-history
flag todebug kustomization
by @matheuscscp in https://github.com/fluxcd/flux2/pull/5541fluxcd/flux2/action
: Determine latest version without using GitHub API by @RussellAult in https://github.com/fluxcd/flux2/pull/5509New 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:
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:
rsa-sha2-512
andrsa-sha2-256
algorithms not being prioritized forssh-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:
flux push artifact --provider=azure
on Azure DevOps runners.knownhosts key mismatch
regression bug in the Flux CLI, source-controller and image-automation-controller.Components changelog
CLI changelog
flux push artifact --provider azure
on DevOps runners by @fluxcdbot in https://github.com/fluxcd/flux2/pull/5396knownhosts key mismatch
regression bug by @fluxcdbot in https://github.com/fluxcd/flux2/pull/5405Full 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:
Components changelog
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:
flux artifact
commandsWaitForTermination
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:
v1.31
>= 1.31.0
v1.32
>= 1.32.0
v1.33
>= 1.33.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.
Upgrade procedure
Upgrade Flux from
v2.5.0
tov2.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:
apiVersion: source.toolkit.fluxcd.io/v1
in the YAML files that containOCIRepository
definitions.api.fluxcd.io/upgrade: "v2.6.0"
to theOCIRepository
resources. (this is not required if Flux Operator is used for upgrade)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
flux trace
for HRs fromOCIRepository
s by @makkes in https://github.com/fluxcd/flux2/pull/5349New 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:
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:
GitRepository
andImageUpdateAutomation
API)Kustomization
API)Kustomization
API)Kustomization
API)Alert
API)Alert
API)Receiver
API)❤️ 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.30
>= 1.30.0
v1.31
>= 1.31.0
v1.32
>= 1.32.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.
Upgrade procedure
Upgrade Flux from
v2.4.0
tov2.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
flux diff
skipping with kustomize-controllerflux debug kustomization
commandflux debug helmrelease
commandfluxcd/pkg
dependenciesConfiguration
📅 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 is behind base branch, 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.