fix(github-release): update flux group to v2.0.1 (patch) #64
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/patch-flux
branch
from
2782d24 to
c3339ca
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/patch-flux
branch
from
c3339ca to
45d0b92
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/patch-flux
branch
from
45d0b92 to
b17dc6a
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/patch-flux
branch
from
b17dc6a to
5009e3d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/patch-flux
branch
from
5009e3d to
fb58f71
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.0.0-rc.1->v2.0.1v2.0.0-rc.1->v2.0.1Release Notes
fluxcd/flux2 (fluxcd/flux2)
v2.0.1Compare Source
Highlights
Flux
v2.0.1is 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(fluxCLI).Components changelog
CLI Changelog
opensslandsha256sum$RUNNER_TOOL_CACHE, support MacOS and Windows, validate checksumNew Documentation
v2.0.0Compare 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.0v1.25>= 1.25.0v1.26>= 1.26.0v1.27>= 1.27.1Note 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.00.15.0API 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.gitImplementationwas removed.spec.accessFromwas removed.status.contentConfigChecksumwas removed.status.artifact.checksumwas removed.status.urlwas 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.commonMetadatawas 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.validationwas removed.spec.patchesStrategicMergewas removed (replaced by.spec.patches).spec.patchesJson6902was 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.urlwas removed (replaced by.status.webhookPath)Upgrade procedure
Upgrade Flux from
v0.xtov2.0.0either 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:
GitRepositoryandKustomizationdefinitions.apiVersion: source.toolkit.fluxcd.io/v1in the YAML files that containGitRepositorydefinitions.apiVersion: kustomize.toolkit.fluxcd.io/v1in the YAML files that contain FluxKustomizationdefinitions.apiVersion: notification.toolkit.fluxcd.io/v1in the YAML files that containReceiverdefinitions.GitRepositoryandKustomizationobjects present in the.spec.resourceslist ofReceiverdefinitions.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 pushexample for ECRgo.modversion with Kubernetes (Go 1.20)flux logsmore lenientv2.0.0-rc.5Compare Source
Highlights
This is the 5th release candidate of Flux v2.0 GA. Users are advised to upgrade from older versions to
v2.0.0-rc.5as soon as possible.Flux
v2.0.0-rc.5addresses a regression that was introduced inv2.0.0-rc.4. This regression caused a disruption in the compatibility with Git servers utilizing v2 of the wire protocol, such as Azure Devops and AWS CodeCommit.💡 For upgrading from v0.x, please see the procedure documented in RC.1.
v2.0.0-rc.4updated all components to use Kustomize v5 and controller-runtime v0.15, both of which contain breaking changes.Fixes and improvements
[controller-runtime] log.SetLogger(...) was never called...(CLI).Components Changelog
CLI Changelog
controller-runtimelogger to a null loggerv2.0.0-rc.4Compare Source
Highlights
This is the 4nd release candidate of Flux v2.0 GA. Users are advised to upgrade from older versions to
v2.0.0-rc.4as soon as possible.Flux v2.0.0-rc.4 comes with support for Kustomize 5.0, Helm 3.12 and Cosign 2.0.
💡 For upgrading from v0.x, please see the procedure documented in RC.1.
Fixes and improvements
flux reconcile source chartfor pulling Helm OCI charts on-demand from container registries (CLI).flux push artifact(CLI)..spec.ref.nameinGitRepository(source-controller).HelmReleaseevents (notification-controller).Components changelog
CLI Changelog
8061827tob98d498v2.0.0-rc.3Compare Source
Highlights
This is the 3rd release candidate of Flux v2.0 GA. Users are advised to upgrade from
v0.41and older versions tov2.0.0-rc.3as soon as possible.Flux v2.0.0-rc.3 comes with security improvements, new features and fixes to issues reported for RC.2.
💡 For upgrading from v0.x, please see the procedure documented in RC.1.
Fixes and improvements
0o744, allowing CI system to run them (source-controller).Alertv1beta2 API has a new optional field.spec.eventMetadatathat allows users to enrich the alerts with information about the cluster name, region, environment, etc. (notification-controller).Components changelog
CLI Changelog
v2.0.0-rc.2Compare Source
Highlights
This is the 2nd release candidate of Flux v2.0 GA. Users are advised to upgrade from
v0.41tov2.0.0-rc.2as soon as possible.Flux v2.0.0-rc.2 comes with fixes to issues reported for RC.1 and performance improvements. Starting with this version, source-controller, kustomize-controller and helm-controller pods are marked as system-cluster-critical. This priority class will reduce the chances of Flux controllers being evicted before other non-critical workloads and prevents the pods from being permanently unavailable.
💡 For upgrading from v0.x, please see the procedure documented in RC.1.
Fixes and improvements
Alertv1beta2 API has a new optional field.spec.inclusionListfor fine-grained control over events filtering (notification-controller)..status.urlwas removed from theReceiverv1 API (notification-controller).Components changelog
CLI Changelog
pull artifactcommandConfiguration
📅 Schedule: Branch creation - "on saturday" (UTC), 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 these updates again.
This PR has been generated by Mend Renovate. View repository job log here.