feat(github-release): update flux group to v2.2.2 (minor) #28
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}
github-actions
bot
added
area/ansible
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/flux
branch
from
df574dd
to
cd8fd38
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.1.2->v2.2.2v2.1.2->v2.2.2Release Notes
fluxcd/flux2 (fluxcd/flux2)
v2.2.2Compare Source
v2.2.1Compare Source
Highlights
Flux v2.2.1 is a patch release that comes with fixes to API backwards compatibility.
Users are encouraged to upgrade for the best experience.
💡 For upgrading to Flux v2.2, please see the procedure documented in 2.2.0.
This version was tested with the latest Kubernetes release, and extends Flux support to Kubernetes v1.29.
The Helm SDK was updated to the latest version, v3.13.3.
Logging in kustomize-controller and helm-controller has been improved to provide faster feedback on any HTTP errors encountered while fetching artifacts from source-controller.
Components changelog
CLI Changelog
v2.2.0Compare Source
Highlights
Flux v2.2.0 is a feature release. Users are encouraged to upgrade for the best experience.
The Flux CLI and controllers have been updated to Kustomize v5.3.0 and Kubernetes v1.28.4.
Flux helm-controller's reconciliation model underwent a significant overhaul, addressing persistent issues such as the automatic recovery of releases stuck in a pending state. In addition, it improves the observability of the release status, and it introduces the ability to enable drift detection on a per-object basis. For more details on the helm-controller improvements, please see the Announcing Flux 2.2 GA blog post.
The Flux CLI can now be used to force or reset the reconciliation state of a
HelmReleasev2beta2 object usingflux reconcile hr --forceandflux reconcile hr --reset.Flux CLI comes with support for bootstrapping Gitea repositories and adds guardrails to
flux installandflux bootstrapto protect users from destructive operations. Theflux versionandflux checkcommands now print the Flux distribution version deployed on the cluster.The Flux alerting capabilities have been extended with NATS and Bitbucket Server & Data Center support.
Starting with this release, Flux minor versions are benchmark to measure the Mean Time To Production (MTTP). The results for this version can be found at
github.com/fluxcd/flux-benchmark.
❤️ 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.26>= 1.26.0v1.27>= 1.27.1v1.28>= 1.28.0Note that Flux may work on older versions of Kubernetes e.g. 1.25, but we don't recommend running end-of-life versions in production nor do we offer support for these versions.
API changes
HelmRelease v2beta2
The HelmRelease kind was promoted from v2beta1 to v2beta2.
The v2beta2 API is backwards compatible with v2beta1, the v2beta1 API is deprecated and will be removed in a future release.
Deprecated fields:
.patchesStrategicMergeand.patchesJson6902Kustomize post-rendering fields have been deprecated in favor of.patches..status.lastAppliedRevisionand.status.lastReleaseRevisionfields have been deprecated in favor of.status.history..status.lastAttemptedValuesChecksumhas been deprecated in favor of.status.lastAttemptedConfigDigest.New fields:
.spec.driftDetection.modefield..spec.driftDetection.ignore.spec.test.filtersfield..status.historyfield. This includes any Helm test results when enabled..status.lastHandledForceAtand.status.lastHandledResetAtfields have been introduced to track the last time a force upgrade or reset was handled.Alert and Provider v1beta3
The Alert and Provider kinds were promoted from v1beta2 to v1beta3.
The v1beta3 API is backwards compatible with v1beta2, the
.statusfield was removed making the resources static objects. Any errors encountered while sending notifications are now recorded as Kubernetes Events associated with the Alert objects.Bucket v1beta2
A new field,
.spec.prefix, has been added to the Bucket API, which enables server-side filtering of files if the object's.spec.provideris set togeneric,awsorgcp.OCIRepository and HelmChart v1beta2
Two new fields,
.spec.verify.matchOIDCIdentity.issuerand.spec.verify.matchOIDCIdentity.subjecthave been added to the HelmChart and OCIRepository APIs. If the image has been keylessly signed via Cosign, these fields can be used to verify the OIDC issuer of the Fulcio certificate and theOIDC identity's subject respectively.
HelmRepository and ImageRepository v1beta2
A new boolean field,
.spec.insecure, has been introduced to theHelmRepository and ImageRepository APIs, which allows connecting to a non-TLS HTTP container registry. For HelmRepositories it is only considered if the object's
.spec.typeis set tooci.From this release onwards, HelmRepository objects of type OCI are treated as static objects, i.e. they have an empty status.
Upgrade procedure
Upgrade Flux from
v2.xtov2.2.0either by rerunning bootstrap or by using the Flux GitHub Action.To upgrade the APIs, make sure the new CRDs and controllers are deployed, and then change the manifests in Git:
apiVersion: helm.toolkit.fluxcd.io/v2beta2in the YAML files that containHelmReleasedefinitions.apiVersion: notification.toolkit.fluxcd.io/v1beta3in the YAML files that containAlertandProviderdefinitions.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.
New Documentation
Components changelog
CLI Changelog
flux reconcile hrcontext deadline exceedederrorflux installfrom overriding bootrapped clusterflux pullwork for OCI artifacts produced by other toolsConfiguration
📅 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.