chore(deps): update helm charts - #659
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Terraform Plan (03-services)→ Resource Changes: 0 to create, 3 to update, 0 to re-create, 0 to delete, 0 ephemeral, 0 to import. ♻️ Update
|
renovate
Bot
force-pushed
the
renovate/helm-charts
branch
from
August 17, 2026 22:47
502355f to
432e5d0
Compare
renovate
Bot
force-pushed
the
renovate/helm-charts
branch
from
August 18, 2026 16:04
432e5d0 to
ca49dd4
Compare
renovate
Bot
force-pushed
the
renovate/helm-charts
branch
from
August 20, 2026 09:46
ca49dd4 to
c3ae6f9
Compare
renovate
Bot
force-pushed
the
renovate/helm-charts
branch
from
August 20, 2026 14:08
c3ae6f9 to
7e359af
Compare
renovate
Bot
force-pushed
the
renovate/helm-charts
branch
from
August 21, 2026 13:44
7e359af to
8dffc34
Compare
renovate
Bot
force-pushed
the
renovate/helm-charts
branch
from
August 28, 2026 11:48
8dffc34 to
a7addff
Compare
renovate
Bot
force-pushed
the
renovate/helm-charts
branch
from
August 28, 2026 16:58
a7addff to
6a414ef
Compare
renovate
Bot
force-pushed
the
renovate/helm-charts
branch
from
August 29, 2026 12:57
6a414ef to
d7fb97e
Compare
This file contains hidden or 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
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:
10.3.2→10.4.21.20.0→1.20.12.3.4→2.4.02.9.0→2.10.03.8.2→3.9.0Release Notes
argoproj/argo-helm (argo-cd)
v10.4.2Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
What's Changed
Full Changelog: argoproj/argo-helm@argo-cd-10.4.1...argo-cd-10.4.2
v10.4.1Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
What's Changed
Full Changelog: argoproj/argo-helm@argo-workflows-2.0.3...argo-cd-10.4.1
v10.4.0Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
What's Changed
Full Changelog: argoproj/argo-helm@argo-workflows-2.0.1...argo-cd-10.4.0
v10.3.3Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
What's Changed
Full Changelog: argoproj/argo-helm@argo-workflows-2.0.0...argo-cd-10.3.3
cilium/cilium (cilium)
v1.20.1: 1.20.1Compare Source
Summary of Changes
Major Changes:
Minor Changes:
Bugfixes:
0as a chart value and templates into configmap. (Backport PR #47885, Upstream PR #47741, @jdw6359)NotAllowedByListenerswhen the TCP listener had an explicitAllowedRoutes.Kindsrestriction. (Backport PR #47690, Upstream PR #46842, @pidreher)CI Changes:
events_map_rate_limitcomplexity coverage (Backport PR #47805, Upstream PR #47691, @pchaigno)Misc Changes:
ct_create{4,6}(Backport PR #47805, Upstream PR #47582, @dylandreimerink)705e964(v1.20) (#47949, @cilium-renovate[bot])7caba52(v1.20) (#47864, @cilium-renovate[bot])reflect.DeepEqualwithassert.Equalin tests (Backport PR #47690, Upstream PR #47424, @HadrienPatte)dc2d74b(v1.20) (#47655, @cilium-renovate[bot])Other Changes:
Docker Manifests
cilium
quay.io/cilium/cilium:v1.20.1@sha256:ae9ea21f7427fe24bc6ea7247eb552157a1b0a431744045d3f641545ca71d11bquay.io/cilium/cilium:stable@sha256:ae9ea21f7427fe24bc6ea7247eb552157a1b0a431744045d3f641545ca71d11bclustermesh-apiserver
quay.io/cilium/clustermesh-apiserver:v1.20.1@sha256:d905d614a332b2058cb81c193e481d1f460902b903f4eb57cc9764640b750fb5quay.io/cilium/clustermesh-apiserver:stable@sha256:d905d614a332b2058cb81c193e481d1f460902b903f4eb57cc9764640b750fb5hubble-relay
quay.io/cilium/hubble-relay:v1.20.1@sha256:59be0ae7d475ab9011a5e954618c0f27b5778b17140381425b308b55ba4917f4quay.io/cilium/hubble-relay:stable@sha256:59be0ae7d475ab9011a5e954618c0f27b5778b17140381425b308b55ba4917f4operator-alibabacloud
quay.io/cilium/operator-alibabacloud:v1.20.1@sha256:2af5dd3d85649ea36d365363b8eca82ad06116c6259c4aace700a7c036348e4cquay.io/cilium/operator-alibabacloud:stable@sha256:2af5dd3d85649ea36d365363b8eca82ad06116c6259c4aace700a7c036348e4coperator-aws
quay.io/cilium/operator-aws:v1.20.1@sha256:7cf0cb0e6584f72ca8de951a1be03829f69fcaeba69dc6c7856fc4470545acd7quay.io/cilium/operator-aws:stable@sha256:7cf0cb0e6584f72ca8de951a1be03829f69fcaeba69dc6c7856fc4470545acd7operator-azure
quay.io/cilium/operator-azure:v1.20.1@sha256:13746a479ca60395df8d83580b49464c6c975cca6fdb21ba4791a076ab01b031quay.io/cilium/operator-azure:stable@sha256:13746a479ca60395df8d83580b49464c6c975cca6fdb21ba4791a076ab01b031operator-generic
quay.io/cilium/operator-generic:v1.20.1@sha256:6c3885fc7b629099fdbe2a5c87869c86feb825fa18fae299eac0f61918d16ecfquay.io/cilium/operator-generic:stable@sha256:6c3885fc7b629099fdbe2a5c87869c86feb825fa18fae299eac0f61918d16ecfoperator
quay.io/cilium/operator:v1.20.1@sha256:67adaf5575902dcce31dc36ba5b5acad397a8b40ec986b55696c94f80b6d861dquay.io/cilium/operator:stable@sha256:67adaf5575902dcce31dc36ba5b5acad397a8b40ec986b55696c94f80b6d861dcrossplane/crossplane (crossplane)
v2.4.0Compare Source
The
v2.4.0release is a regular quarterly Crossplane release that is focused on maturing a number of key areas of functionality across the project, as Crossplane continues to become more capable, more reliable, and more performant for your production workloads. This release includes the ability to watch required resources and reconcile XRs immediately when they change, scale to zero for safe-start capable providers, release artifacts that are vulnerability scannable, and a wide range of fixes and reliability improvements. It also includes security fixes in Crossplane's Go toolchain and dependencies.🚨 v1.20 end-of-life (EOL) November 2026
This v2.4 release marks the final release cycle where v1.20 will be maintained.
When v2.5 is released in Nov 2026, v1.20 will reach its EOL and no longer receive any support or maintenance by the Crossplane project. Until that time, we will continue to provide critical fixes and security related dependency updates to v1.20.
Is your control plane ready for v2?
Upgrading to Crossplane v2 does not require any migration as part of the upgrade process, with the exception of the minimal breaking changes explicitly called out in the v2 documentation. If your control plane is not affected by those changes, you can simply upgrade to v2 right away.
To better assist Crossplane users in determining if their control planes are affected by any of the breaking changes in v2, we have released a v2 readiness checker tool in the v1.20 Crossplane CLI that can be invoked via
crossplane beta upgrade check. You can read all about this tool in the following resources:Crossplane Downstream Distributions
Downstream distributions are eligible to continue their extended support and maintenance for their releases that are based on upstream Crossplane's v1.20. Check with your vendor for more details if you are using a downstream distribution of Crossplane.
🚨 v2.4 Notable and Breaking Changes
releases.crossplane.io. New CLI releases go only tocli.crossplane.io, under the binary namecrossplanerather thancrank. This completes the CLI's move to https://github.com/crossplane/cli, which was announced in thev2.3.0release notes and dual published to both locations forv2.3.0to ease the transition.releases.crossplane.io, update them to usecli.crossplane.io, and update any firewall or proxy rule that allowsreleases.crossplane.ioto now allowcli.crossplane.ioinstead.install.shscript as their installation procedure are unaffected.metadata.generation, so any change to a package's spec produces a newPackageRevision. #7473runtimeConfigRefreused the existing revision, along with its stale runtime settings. #5068v2.4, every installed package gets a new revision, with a new name, on its first reconcile.PodsforProvidersandFunctionswill be restarted for this new revision.Deployment,ServiceAccount,Service, and TLSSecrets) are now applied with server-side apply under thepkg.crossplane.io/runtimefield manager, replacing the previous merge patch applicator. #7563DeploymentRuntimeConfigis now removed from the live runtime object, rather than lingering until that object is replaced. #4817RUNTIMEprinter column onProviderRevisionandFunctionRevisionwas renamed toRUNTIME-HEALTHY, and a newRUNTIME-ACTIVEcolumn was added. #7586kubectl get providerrevisionorkubectl get functionrevisionoutput by column position.typelabel on theengine_watches_started_totalandengine_watches_stopped_totalmetrics changed fromComposedResourcetoDependency, now that a single watch mechanism covers both composed and required resources. #7572🎉 Highlights
design/one-pager-watching-required-resources.mdand #7572.ManagedResourceDefinitionsare inactive, so there is no reason to run its pods. Crossplane now creates such a provider's runtimeDeploymentwith zero replicas and scales it up once its first MRD becomes active, such as through a matchingManagedResourceActivationPolicy. Installing a broad set of providers no longer costs you a running pod for each one that has nothing to reconcile yet. #7586RuntimeActivecondition onProviderRevisionandFunctionRevisionmakes this visible. It isFalsewith reasonAwaitingActivationwhile the runtime is intentionally scaled to zero andTrueonce it has been scaled up.RuntimeHealthystays healthy in both cases, and the package'sHealthycondition surfaces the awaiting state with the same reason.spec.replicasin aDeploymentRuntimeConfig, which is now read as how many replicas to run while running, rather than a demand to always be running. #7639buildGoModule, which includes the full Go dependency list into the binary. Scanners such asgrypeandtrivypreviously were only able to discover the Crossplane main module and the Go standard library, so CVEs in our third-party dependencies were not visible to them. Now Crossplane and its complete set of dependencies are visible to security scanner tools. #7549DeploymentRuntimeConfigis now actually removed from the liveDeploymentinstead of lingering (#7563, fixing #4817). Deactivating a revision also no longer deletes a runtimeDeploymentthat another revision controls, which could happen when aDeploymentRuntimeConfigpins a stabledeploymentTemplate.metadata.name(#7561).spec.resourceRefscan no longer be used to make the composite controller delete arbitrary resources (#7627). The claim to XR syncers now strip XR machinery fields such asresourceRefsand thecrossplanestanza, which a claim could otherwise smuggle through an XRD schema that setsx-kubernetes-preserve-unknown-fields: true(#7626)./v1.20/, used to return results from all versions, potentially returning features and APIs that don't exist in the version you're actually reading. Search is now scoped to the version you're on, results carry a clearly visible version badge, and pages from older versions show a banner explaining that, with a link to latest. Thanks to @haarchri for this one in crossplane/docs#1051, so give it a try at https://docs.crossplane.io.crossplane render: an XRD schema can now be supplied tocrossplane internal render(#7452), requirements are returned even when a function returns a fatal result (#7455), a namespace is set on injected resource references only for cluster-scoped XRs, matching the real reconciler (#7523), and an input XR fetched from a real cluster keeps its own UID so its observed resources are read correctly, with clear errors when observed resources don't line up with the XR (#7544).sha256files published with release binaries are now calculated after Nix strips the binary, so amd64 checksums match what you download. They didn't forv2.2.0throughv2.3.1, and CI now verifies checksums before uploading artifacts. #7660Usageno longer gets a redundant owner update on every reconcile, which could repeatedly trigger composition reconciliation and eventually open the XR circuit breaker. #7591spec.resourceRefsnow includes the namespace, so references stay stable when composed resources share a name across namespaces. #7341🏅 Release MVP
For the v2.4 release cycle, we'd like to recognize @rafal-jan as the release MVP!
They had an enormous impact in
crossplane-runtime, first by diagnosing the root cause in crossplane/crossplane-runtime#1056 of significant memory usage by providers that are safe-start capable when they essentially watch and cache every CRD in the control plane. Then @rafal-jan went a step further and submitted an elegant solution in crossplane/crossplane-runtime#1058 to strip the cached CRDs down to just the fields needed to watch and respond appropriately to events, drastically reducing the memory consumption by these providers. Thank you @rafal-jan!📖 Full Changelog
internal renderby @jcogilvie in #7452eb5cf3a(main) by @crossplane-renovate[bot] in #7379fee1f7d(main) by @crossplane-renovate[bot] in #73101201ddd(main) by @crossplane-renovate[bot] in #7128fd21066(main) by @crossplane-renovate[bot] in #7380df4cb1c(main) by @crossplane-renovate[bot] in #74839c8100a(main) by @crossplane-renovate[bot] in #74878aad20d(main) by @crossplane-renovate[bot] in #74860fb7174(main) by @crossplane-renovate[bot] in #74858aa0397(main) by @crossplane-renovate[bot] in #748439bae1e(main) by @crossplane-renovate[bot] in #7488Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.