fix(github-release): update fluxcd/flux2 to v2.0.0-rc.3 #715
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.0-rc.3
Release Notes
fluxcd/flux2
v2.0.0-rc.3
Compare Source
Highlights
This is the 3rd release candidate of Flux v2.0 GA. Users are advised to upgrade from
v0.41
and older versions tov2.0.0-rc.3
as 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).Alert
v1beta2 API has a new optional field.spec.eventMetadata
that 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.2
Compare Source
Highlights
This is the 2nd release candidate of Flux v2.0 GA. Users are advised to upgrade from
v0.41
tov2.0.0-rc.2
as 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
Alert
v1beta2 API has a new optional field.spec.inclusionList
for fine-grained control over events filtering (notification-controller)..status.url
was removed from theReceiver
v1 API (notification-controller).Components changelog
CLI Changelog
pull artifact
commandConfiguration
📅 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.