Update dependency fluxcd/flux2 to v2 #12
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:
v0.41.2
->v2.0.1
Release Notes
fluxcd/flux2
v2.0.1
Compare Source
Highlights
Flux
v2.0.1
is a patch release which comes with various fixes. Users are encouraged to upgrade for the best experience.💡 For upgrading from Flux
v0.x
, please see the procedure documented in 2.0.0.Fixes
source-controller
,image-reflector-controller
).kustomize-controller
).flux diff ks --kustomization-file
(flux
CLI).Components changelog
CLI Changelog
openssl
andsha256sum
$RUNNER_TOOL_CACHE
, support MacOS and Windows, validate checksumNew Documentation
v2.0.0
Compare Source
Highlights
This is the first General Availability (GA) release of Flux v2.
Flux v2.0.0 comes with the promotion of the GitOps related APIs to v1 and adds horizontal scaling & sharding capabilities to Flux controllers. The Git bootstrap capabilities provided by the Flux CLI and by Flux Terraform Provider are now considered stable and production ready.
Starting with this version, the build, release and provenance portions of the Flux project supply chain provisionally meet SLSA Build Level 3.
Flux GA is fully integrated with Kubernetes Workload Identity for AWS, Azure and Google Cloud to facilitate passwordless authentication to OCI sources (container images, OCI artifacts, Helm charts).
The Flux alerting capabilities have been extended with PagerDuty and Google Pub/Sub support. The improved Alert v1beta2 API provides better control over events filtering and allows users to enrich the alerts with custom metadata.
Supported versions
Starting with this version, the Flux CLI and the GA components (source-controller, kustomize-controller and notification-controller) follow the release cadence and support pledge documented in the Flux release specification.
Kubernetes compatibility
This release is compatible with the following Kubernetes versions:
v1.24
>= 1.24.0
v1.25
>= 1.25.0
v1.26
>= 1.26.0
v1.27
>= 1.27.1
Note that Flux may work on older versions of Kubernetes e.g. 1.19, but we don't recommend running end-of-life versions in production nor do we offer support for these versions.
Flux ecosystem support
The following (open-source) extensions & integrations are compatible with this Flux release, starting from the specified minimum version or higher.
0.26.0
0.15.0
API changes
GitRepository v1
The GitRepository kind was promoted from v1beta2 to v1 (GA) and deprecated fields were removed.
The v1 API is backwards compatible with v1beta2, except for the following:
.spec.gitImplementation
was removed.spec.accessFrom
was removed.status.contentConfigChecksum
was removed.status.artifact.checksum
was removed.status.url
was removed (replaced by.status.artifact.url
)Kustomization v1
The Kustomization kind was promoted from v1beta2 to v1 (GA) and deprecated fields were removed.
A new optional field
.spec.commonMetadata
was added to the API for setting labels and/or annotations to all resources part of a Kustomization.The v1 API is backwards compatible with v1beta2, except for the following:
.spec.validation
was removed.spec.patchesStrategicMerge
was removed (replaced by.spec.patches
).spec.patchesJson6902
was removed (replaced by.spec.patches
)Receiver v1
The Receiver kind was promoted from v1beta2 to v1 (GA) and deprecated fields were removed.
The v1 API is backwards compatible with v1beta2, except for the following:
.status.url
was removed (replaced by.status.webhookPath
)Upgrade procedure
Upgrade Flux from
v0.x
tov2.0.0
either by rerunning bootstrap or by using the Flux GitHub Action.To upgrade the APIs from v1beta2, make sure the new CRDs and controllers are deployed, and then change the manifests in Git:
GitRepository
andKustomization
definitions.apiVersion: source.toolkit.fluxcd.io/v1
in the YAML files that containGitRepository
definitions.apiVersion: kustomize.toolkit.fluxcd.io/v1
in the YAML files that contain FluxKustomization
definitions.apiVersion: notification.toolkit.fluxcd.io/v1
in the YAML files that containReceiver
definitions.Bumping the APIs version in manifests can be done gradually. It is advised to not delay this procedure as the beta versions will be removed after 6 months.
New Documentation
❤️ Big thanks to all the Flux contributors that helped us reach this milestone!
👏 And a special shoutout to the Flux community who supported us over the years!
Components changelog
CLI Changelog
flux push
example for ECRgo.mod
version with Kubernetes (Go 1.20)flux logs
more lenientConfiguration
📅 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.