chore(deps): update dependency fluxcd/flux2 to v2.7.0 #22
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.6.4
->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 #5379flux push artifact --provider azure
on DevOps runners by @matheuscscp in #5390knownhosts key mismatch
regression bug by @matheuscscp in #5404normalize.UnstructuredList
instead ofssa.SetNativeKindsDefaults
by @cappyzawa in #5407flux create tenant
by @reiSh6phoo9o in #5402flux push artifact
for insecure registries by @stefanprodan in #5449flux diff kustomization
ignore patterns by @dgunzy in #5451app.kubernetes.io/part-of: flux
label to controller pods by @pinkavaj in #5440flux migrate
command by @stefanprodan in #5473GOMAXPROCS
by @stefanprodan in #5501--all-namespaces
flag by @mohiuddin-khan-shiam in #5414--show-history
flag todebug helmrelease
by @hawkaii in #5505ArtifactGenerator
kind by @stefanprodan in #5520flux [reconcile|suspend|resume] image policy
commands by @lukas8219 in #5492force: enabled
annotation influx diff ks
command by @stefanprodan in #5528fluxcd/gha-workflows
by @stefanprodan in #5529ArtifactGenerators
during uninstall by @stefanprodan in #5531ExternalArtifact
toflux trace
by @stefanprodan in #5532--show-history
flag todebug kustomization
by @matheuscscp in #5541fluxcd/flux2/action
: Determine latest version without using GitHub API by @RussellAult in #5509New Contributors
Full Changelog: fluxcd/flux2@v2.6.0...v2.7.0
Configuration
📅 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.