Update Flux group to v2.1.1 (minor) #30
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/flux"
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:
v2.0.1
->v2.1.1
v2.0.1
->v2.1.1
Release Notes
fluxcd/flux2 (fluxcd/flux2)
v2.1.1
Compare Source
Highlights
Flux
v2.1.1
is 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
).nil
artifact before loading Helm charts (helm-controller
).flux
CLI).Components changelog
CLI Changelog
v2.1.0
Compare 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
,keyFile
andcertFile
keys.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-metrics
CRD exporter to report metrics containing rich information about Flux reconciliation status e.g. Git revision, Helm chart version, OCI artifacts digests, etc. Thegotk_reconcile_condition
metrics 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.name
is an optional field used to specify the name of a Kubernetes Secret that contains the HTTP/S or SOCKS5 proxy settings..spec.verify.mode
now support one of the following valuesHEAD
,Tag
,TagAndHEAD
.Kustomization v1
The Kustomization API was extended with two apply policies
IfNotPresent
andIgnore
.Changing the apply behaviour for specific Kubernetes resources, can be done using the following annotations:
kustomize.toolkit.fluxcd.io/ssa
Override
Override
-
Merge
-
IfNotPresent
-
Ignore
kustomize.toolkit.fluxcd.io/force
Disabled
Enabled
-
Disabled
kustomize.toolkit.fluxcd.io/prune
Enabled
Enabled
-
Disabled
The
IfNotPresent
policy instructs the controller to only apply the Kubernetes resources if they are not present on the cluster.This policy can be used for Kubernetes
Secrets
andValidatingWebhookConfigurations
managed 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.refspec
is an optional field used to specify a Git refspec used when pushing commits upstream..spec.git.push.options
is 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.secretRef
has been deprecated in favor of a new field.spec.certSecretRef
.caFile
,keyFile
andcertFile
keys in the Secret specified in.spec.certSecretRef
have been deprecated in favor ofca.crt
,tls.key
andtls.crt
.caFile
,keyFile
andcertFile
keys in the Secret specified in.spec.certSecretRef
have been deprecated in favor ofca.crt
,tls.key
andtls.crt
..spec.secretRef
using theca.crt
key, which takes precedence over thecaFile
key.Upgrade procedure
Upgrade Flux from
v2.0.x
tov2.1.0
either by rerunning bootstrap or by using the Flux GitHub Action.To upgrade Flux from
v0.x
tov2.1.0
please follow the Flux GA upgrade procedure.Kubernetes compatibility
This release is compatible with the following Kubernetes versions:
v1.25
>= 1.25.0
v1.26
>= 1.26.0
v1.27
>= 1.27.1
v1.28
>= 1.28.0
Note 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-bits
flagopenssl
andsha256sum
$RUNNER_TOOL_CACHE
, support MacOS and Windows, validate checksumConfiguration
📅 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 these updates again.
This PR has been generated by Renovate Bot.
bf423d41f3
toc0f150bfb2
c0f150bfb2
tobcb5933c18
Update Flux group to v2.1.0 (minor)to Update Flux group to v2.1.1 (minor)bcb5933c18
to92cb481567