chore(deps): update flux group to v2.2.3 (minor) #25
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}
dettanym
force-pushed
the
main
branch
8 times, most recently
from
8b42dc3 to
712883b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/flux
branch
from
9edc18a to
b129e3d
Compare
dettanym
force-pushed
the
main
branch
4 times, most recently
from
2a006c9 to
4d9cc8b
Compare
renovate
bot
force-pushed
the
renovate/flux
branch
from
b129e3d to
b248e64
Compare
|
Follow this link (from the release notes above): https://github.com/fluxcd/flux2/releases/tag/v2.0.0#upgrade |
1 task
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/flux
branch
from
b248e64 to
9ccba79
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/flux
branch
from
9ccba79 to
1e3e874
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/flux
branch
from
1e3e874 to
a90c506
Compare
renovate
bot
force-pushed
the
renovate/flux
branch
from
a90c506 to
47bc0bb
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/flux
branch
from
47bc0bb to
c8da996
Compare
renovate
bot
changed the title
|
Squashed commits in main branch. Now the merged commit is d419a40 |
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.2.3v2.0.0-rc.1->v2.2.3Release Notes
fluxcd/flux2 (fluxcd/flux2)
v2.2.3Compare Source
Highlights
Flux v2.2.3 is a patch release which comes with various fixes and improvements. 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 release updates the Kubernetes dependencies to v1.28.6 and various other dependencies to their latest version to patch upstream CVEs.
All controllers are built with Go 1.21.6 using Alpine Linux 3.19.1 base image.
Fixes:
RolesandClusterRoleswith aggregated roles were continuous reconciled by kustomize-controller has been fixed.See the components changelog for a full list of bug fixes.
Components changelog
CLI Changelog
flux checkshould error on unrecognised argsflux statsshould error on unrecognised argsv2.2.2Compare Source
Highlights
Flux v2.2.2 is a patch release that addresses an issue with the label selector sharding functionality in the helm-controller. Users are encouraged to upgrade for the best experience.
💡 For upgrading to Flux v2.2, please see the procedure documented in 2.2.0.
Components changelog
CLI Changelog
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 toolsv2.1.2Compare Source
Highlights
Flux
v2.1.2is a patch release which comes with various fixes. Users are encouraged to upgrade for the best experience.Fixes
KustomizationandHelmReleaseresources when the source-controller has restarted and is working on restoring the storage.OCIRepositorieswhen artifacts contain symlinks.Kustomizations.flux bootstrapwhen the owner doesn't match the identity associated with the given token.flux pull artifactto fetch OCI artifacts produced by other tools.Components changelog
CLI Changelog
flux pullwork for OCI artifacts produced by other toolsv2.1.1Compare Source
Highlights
Flux
v2.1.1is a patch release which comes with various fixes. Users are encouraged to upgrade for the best experience.Fixes
source-controller)..spec.secretRef(source-controller).image-automation-controller).helm-controller).helm-controller).nilartifact before loading Helm charts (helm-controller).fluxCLI).Components changelog
CLI Changelog
v2.1.0Compare Source
Highlights
Flux v2.1.0 is a feature release. Users are encouraged to upgrade for the best experience.
The Flux APIs were extended with new opt-in features in a backwards-compatible manner.
The Flux Git capabilities have been improved with support for Git push options, Git refspec, Gerrit, HTTP/S and SOCKS5 proxies.
The Flux alerting capabilities have been extended with Datadog support.
The Flux controllers come with performance improvements when reconciling Helm repositories with large indexes (80% memory reduction), and when reconciling Flux Kustomizations with thousands of resources (x4 faster server-side apply). The load distribution has been improved when reconciling Flux objects in parallel to reduce CPU and memory spikes.
❤️ Big thanks to all the Flux contributors that helped us with this release!
Deprecations
Flux v2.1.0 comes with support for Kubernetes TLS Secrets when referring to secrets containing TLS certs, and deprecates the usage of
caFile,keyFileandcertFilekeys.For more details about the TLS changes please see the Kubernetes TLS Secrets section.
Flux v2.1.0 comes with major improvements to the Prometheus monitoring stack. Starting with this version, Flux is leveraging the
kube-state-metricsCRD exporter to report metrics containing rich information about Flux reconciliation status e.g. Git revision, Helm chart version, OCI artifacts digests, etc. Thegotk_reconcile_conditionmetrics was deprecated in favor of thegotk_resource_info.For more details about the new monitoring stack please see the Flux Prometheus metrics documentation and the flux2-monitoring-example repository.
API changes
GitRepository v1
The GitRepository API was extended with the following fields:
.spec.proxySecretRef.nameis an optional field used to specify the name of a Kubernetes Secret that contains the HTTP/S or SOCKS5 proxy settings..spec.verify.modenow support one of the following valuesHEAD,Tag,TagAndHEAD.Kustomization v1
The Kustomization API was extended with two apply policies
IfNotPresentandIgnore.Changing the apply behaviour for specific Kubernetes resources, can be done using the following annotations:
kustomize.toolkit.fluxcd.io/ssaOverrideOverride-
Merge-
IfNotPresent-
Ignorekustomize.toolkit.fluxcd.io/forceDisabledEnabled-
Disabledkustomize.toolkit.fluxcd.io/pruneEnabledEnabled-
DisabledThe
IfNotPresentpolicy instructs the controller to only apply the Kubernetes resources if they are not present on the cluster.This policy can be used for Kubernetes
SecretsandValidatingWebhookConfigurationsmanaged by cert-manager,where Flux creates the resources with fields that are later on mutated by other controllers.
ImageUpdateAutomation v1beta1
The ImageUpdateAutomation was extended with the following fields:
.spec.git.push.refspecis an optional field used to specify a Git refspec used when pushing commits upstream..spec.git.push.optionsis an optional field used to specify the Git push options to be sent to the Git server when pushing commits upstream.Kubernetes TLS Secrets
All the Flux APIs that accept TLS data have been modified to adopt Secrets of type
kubernetes.io/tls. This includes:.spec.secretRefhas been deprecated in favor of a new field.spec.certSecretRef.caFile,keyFileandcertFilekeys in the Secret specified in.spec.certSecretRefhave been deprecated in favor ofca.crt,tls.keyandtls.crt.caFile,keyFileandcertFilekeys in the Secret specified in.spec.certSecretRefhave been deprecated in favor ofca.crt,tls.keyandtls.crt..spec.secretRefusing theca.crtkey, which takes precedence over thecaFilekey.Upgrade procedure
Upgrade Flux from
v2.0.xtov2.1.0either by rerunning bootstrap or by using the Flux GitHub Action.To upgrade Flux from
v0.xtov2.1.0please follow the Flux GA upgrade procedure.Kubernetes compatibility
This release is compatible with the following Kubernetes versions:
v1.25>= 1.25.0v1.26>= 1.26.0v1.27>= 1.27.1v1.28>= 1.28.0Note that Flux may work on older versions of Kubernetes e.g. 1.21, but we don't recommend running end-of-life versions in production nor do we offer support for these versions.
New Documentation
Components changelog
CLI Changelog
--ssh-rsa-bitsflagopensslandsha256sum$RUNNER_TOOL_CACHE, support MacOS and Windows, validate checksumv2.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.
Configuration
📅 Schedule: Branch creation - "on tuesday" (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.