Repository navigation
chore(deps): update helm release cilium to v1.20.4 - #97
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
February 4, 2025 16:51
0edc892 to
8d53264
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
February 13, 2025 10:30
8d53264 to
c0a62d7
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
March 15, 2025 14:37
c0a62d7 to
89f7834
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
April 14, 2025 22:38
89f7834 to
1be99cd
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
May 15, 2025 20:11
1be99cd to
b3d383f
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
June 19, 2025 22:43
b3d383f to
49855d3
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
July 16, 2025 13:41
49855d3 to
715f361
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
July 30, 2025 00:46
715f361 to
2388b52
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
2 times, most recently
from
August 15, 2025 18:48
aee55c7 to
1a35f25
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
September 17, 2025 16:51
1a35f25 to
50bcb85
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
October 24, 2025 02:29
50bcb85 to
19a3b1b
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
November 12, 2025 19:50
19a3b1b to
6d5a813
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
December 17, 2025 14:48
6d5a813 to
94eef2f
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
January 13, 2026 11:11
94eef2f to
aa10d92
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
February 4, 2026 05:36
aa10d92 to
2e6d0a9
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
February 17, 2026 21:51
2e6d0a9 to
9b9b74f
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
March 23, 2026 13:48
9b9b74f to
cbf10a6
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
April 16, 2026 08:53
cbf10a6 to
19d3d6f
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
May 13, 2026 20:29
19d3d6f to
edb9568
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
June 16, 2026 17:01
edb9568 to
8334ff6
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
July 16, 2026 17:42
8334ff6 to
a468991
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
July 29, 2026 18:36
a468991 to
ef96d7a
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
August 18, 2026 13:08
ef96d7a to
9b69ade
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
September 16, 2026 04:50
9b69ade to
1f42cda
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
October 15, 2026 16:12
1f42cda to
17297a3
Compare
renovate
Bot
force-pushed
the
renovate/cilium-1.x
branch
from
October 23, 2026 18:50
17297a3 to
650aefd
Compare
This branch has not been deployed
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
1.16.5→1.20.4Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
cilium/cilium (cilium)
v1.20.4: 1.20.4Compare Source
Security patch release
Out-of-band security patch release to fix CVE-2026-111943 (golang/go#82345): upgrades Go to 1.26.10 so that the compromised eMudhra intermediate CA certificates are no longer trusted, and updates all dependencies to their latest patch versions.
Summary of Changes
Minor Changes:
Bugfixes:
CI Changes:
Misc Changes:
Other Changes:
Docker Manifests
cilium
quay.io/cilium/cilium:v1.20.4@sha256:20fe92e4c86641233a450098c158d2d29085f3419931ab6bf681d2485dedf16equay.io/cilium/cilium:stable@sha256:20fe92e4c86641233a450098c158d2d29085f3419931ab6bf681d2485dedf16eclustermesh-apiserver
quay.io/cilium/clustermesh-apiserver:v1.20.4@sha256:aeac78ae77d166b86630310f2eb53fbc92014eda36ada8e6b2d7f2b8f2dadbfaquay.io/cilium/clustermesh-apiserver:stable@sha256:aeac78ae77d166b86630310f2eb53fbc92014eda36ada8e6b2d7f2b8f2dadbfahubble-relay
quay.io/cilium/hubble-relay:v1.20.4@sha256:cb23408209697ed30d2bc462e1f01eb622ea4423a891458f78bc88d7255bbfc1quay.io/cilium/hubble-relay:stable@sha256:cb23408209697ed30d2bc462e1f01eb622ea4423a891458f78bc88d7255bbfc1operator-alibabacloud
quay.io/cilium/operator-alibabacloud:v1.20.4@sha256:163a08ee4438780638899742e95521e1a37edeb676c6e5c924d320c4c0bd09adquay.io/cilium/operator-alibabacloud:stable@sha256:163a08ee4438780638899742e95521e1a37edeb676c6e5c924d320c4c0bd09adoperator-aws
quay.io/cilium/operator-aws:v1.20.4@sha256:caab27c6e3286a596d502f76aa6cffe2efab6e8a92234a0d10d2eed3eda85c7cquay.io/cilium/operator-aws:stable@sha256:caab27c6e3286a596d502f76aa6cffe2efab6e8a92234a0d10d2eed3eda85c7coperator-azure
quay.io/cilium/operator-azure:v1.20.4@sha256:0669c35e9f1638bbdd6cf5c64163e7ee4ea4ef440e223050e60665811369b4ecquay.io/cilium/operator-azure:stable@sha256:0669c35e9f1638bbdd6cf5c64163e7ee4ea4ef440e223050e60665811369b4ecoperator-generic
quay.io/cilium/operator-generic:v1.20.4@sha256:7a7a3489dc66ad67e420d285c8a8d2e169b0957ad15e120f593d27081bf38d82quay.io/cilium/operator-generic:stable@sha256:7a7a3489dc66ad67e420d285c8a8d2e169b0957ad15e120f593d27081bf38d82operator
quay.io/cilium/operator:v1.20.4@sha256:f94e9812f191e0c31b5cfe6cb1f38f5c349d4f159f2030e621d179d826257263quay.io/cilium/operator:stable@sha256:f94e9812f191e0c31b5cfe6cb1f38f5c349d4f159f2030e621d179d826257263v1.20.3: 1.20.3Compare Source
Summary of Changes
Minor Changes:
Bugfixes:
redirectBackend.toPortsis declared as an empty array. The agent will now reject such a policy. (Backport PR #48907, Upstream PR #48491, @ajmmm)hubble.tls.auto.privateKeysettings are no longer ignored in Hubble cert-manager certificates (Backport PR #49189, Upstream PR #49114, @byxorna)metrics listdefault address to work on IPv6-only clusters with dual stack nodes by trying both IPv4 and IPv6 loopback addresses (Backport PR #48907, Upstream PR #48780, @41ks)CI Changes:
Test NodePort with L7 policytests (Backport PR #49067, Upstream PR #46499, @smagnani96)Misc Changes:
fd7dc98(v1.20) (#49035, @cilium-renovate[bot])0f063af(v1.20) (#49149, @cilium-renovate[bot])6c2a553(v1.20) (#48879, @cilium-renovate[bot])d772206(v1.20) (#49298, @cilium-renovate[bot])Other Changes:
Docker Manifests
cilium
quay.io/cilium/cilium:v1.20.3@sha256:95cfa5c2427cc6b452c00908778d0566311f572589284af949d06a013db1a849quay.io/cilium/cilium:stable@sha256:95cfa5c2427cc6b452c00908778d0566311f572589284af949d06a013db1a849clustermesh-apiserver
quay.io/cilium/clustermesh-apiserver:v1.20.3@sha256:5c8dca0d0b77bb593df157be39f6c9c868dc08922bbd0540ac0a56815341b227quay.io/cilium/clustermesh-apiserver:stable@sha256:5c8dca0d0b77bb593df157be39f6c9c868dc08922bbd0540ac0a56815341b227hubble-relay
quay.io/cilium/hubble-relay:v1.20.3@sha256:c6f819d9c5e0b35ccac63b9f2f1ae213fd9be50588e15d5a444d5d305ad317b5quay.io/cilium/hubble-relay:stable@sha256:c6f819d9c5e0b35ccac63b9f2f1ae213fd9be50588e15d5a444d5d305ad317b5operator-alibabacloud
quay.io/cilium/operator-alibabacloud:v1.20.3@sha256:615f8c2995e437320571d6f61e623d6848ed3ea357cdaa886ac95bbff29a0b52quay.io/cilium/operator-alibabacloud:stable@sha256:615f8c2995e437320571d6f61e623d6848ed3ea357cdaa886ac95bbff29a0b52operator-aws
quay.io/cilium/operator-aws:v1.20.3@sha256:49bdd1d54bdf3da2740848c4662854d0d41c0df25cffe8575d71723db08cc0d1quay.io/cilium/operator-aws:stable@sha256:49bdd1d54bdf3da2740848c4662854d0d41c0df25cffe8575d71723db08cc0d1operator-azure
quay.io/cilium/operator-azure:v1.20.3@sha256:7132b3ff7e33a076ea9fadaa6e4f2b364937ed7b118b92928bdb4706921a2ffaquay.io/cilium/operator-azure:stable@sha256:7132b3ff7e33a076ea9fadaa6e4f2b364937ed7b118b92928bdb4706921a2ffaoperator-generic
quay.io/cilium/operator-generic:v1.20.3@sha256:efdd8d89d6d8f63d21a065fa2f9e17614a2b3ac9371b221af9355f63829e2dbcquay.io/cilium/operator-generic:stable@sha256:efdd8d89d6d8f63d21a065fa2f9e17614a2b3ac9371b221af9355f63829e2dbcoperator
quay.io/cilium/operator:v1.20.3@sha256:c40996c8a413f57db75715e683abc550e7849904aa20b8730822ba532f9b783cquay.io/cilium/operator:stable@sha256:c40996c8a413f57db75715e683abc550e7849904aa20b8730822ba532f9b783cv1.20.2: 1.20.2Compare Source
Summary of Changes
Minor Changes:
Bugfixes:
defaultGatewaypeer auto-discovery selecting a default route from a non-main routing table, such as thedefault via cilium_hostroute Cilium installs in the from-proxy table, instead of the node's real default gateway. (Backport PR #48418, Upstream PR #47971, @ecbaldwin)fatal error: concurrent map iteration and map write) when an endpoint's policy was recomputed while incremental policy map changes were applied concurrently. Most commonly triggered by named-port policies under pod churn. (Backport PR #48735, Upstream PR #48098, @nashant)vtep-sync-interval,enable-xt-socket-fallback,eni-delete-on-terminationwith a custom CNI configuration, theenableIdentityMarkHelm value outside CNI chaining mode, andlb-retry-backoff-max. (Backport PR #48434, Upstream PR #47635, @aanm)CI Changes:
Configuration
📅 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.