Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update module github.com/cilium/cilium to v1.15.0-pre.2 #1724

Merged
merged 1 commit into from
Nov 6, 2023

Conversation

cilium-renovate[bot]
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
github.com/cilium/cilium require patch v1.15.0-pre.1 -> v1.15.0-pre.2

Release Notes

cilium/cilium (github.com/cilium/cilium)

v1.15.0-pre.2: 1.15.0-pre.2

Compare Source

Summary of Changes

Major Changes:

Minor Changes:

Bugfixes:

  • Always replace the cilium_call_* tail call map during upgrade/restart to avoid "Missed tail call" errors (#​28740, @​ti-mo)
  • backporting: Revert changes until the new workflow will be in place (#​28371, @​pippolo84)
  • bpf: fixes an issue where inserting inner maps into an outer may fail with EINVAL due to flags mismatch (#​28710, @​ldelossa)
  • bpf: overlay: fix missing DBG_DECAP for Inter-Cluster-SNAT (#​28466, @​julianwiedmann)
  • Don't bind a /64 address to cilium_host to avoid misrouting cross-node traffic (#​28633, @​CallMeFoxie)
  • Don't orphan CEPs when node IPV6 is preferred at dual stack k8s config (#​28142, @​rawmind0)
  • envoy: fix lb backend endpoint calculation (#​27923, @​mhofstetter)
  • Fix a bug that causes pod-to-pod traffic between nodes to be dropped when IPsec is enabled and kube-proxy installed rules in both iptables-nft and iptables-legacy. (#​28258, @​pchaigno)
  • Fix CIDR labels computation (#​28788, @​pippolo84)
  • Fix concurrency issue when changing labels on pods started before Cilium setup their network. Cilium will now process pod labels modified while setting up the pod network. (#​28789, @​aanm)
  • Fix Helm rendering for dashboards.enabled=true (#​28542, @​bakito)
  • Fix incorrect logic used by the Ingress Controller to sync Cilium's IngressClass on startup. (#​28663, @​learnitall)
  • Fix issue causing KVStoreMesh metrics to be included in the dedicated Service/ServiceMonitor when KVStoreMesh is disabled (#​28481, @​giorio94)
  • Fix wrong host and router IP being used for some IPv6 deployments, which was causing various connectivity problems. (#​28417, @​ti-mo)
  • Fix wrong host and router IP being used for some IPv6 deployments, which was causing various connectivity problems. (Backport PR #​28500, Upstream PR #​28417, @​ti-mo)
  • fix: Correct spire labels identation in helm chart (#​28610, @​sayboras)
  • Fix: Gateway API double slash while stripping path prefix (#​28294, @​nxy7)
  • fixed cilium-operator delete CEC cilium-ingress when other ingressclass resources are created (#​28638, @​chaunceyjiang)
  • gateway-api: fix empty URI when removing path prefix (#​28606, @​dddddai)
  • helm: Correct command for initContainer config (#​28613, @​sayboras)
  • Improved event handling for pod events by removing an unnecessary early return, allowing unrelated components to execute correctly, while enhancing ipcache error logging. (#​28840, @​aanm)
  • ipcache: fix flapping labels in SelectorCache when reserved:host identity has multiple IPs (#​28332, @​squeed)
  • pkg/k8s: use a deep copy of CNP in UpdateStatus to avoid race condition (#​28364, @​aanm)
  • Print full labelset for all identities in 'cilium ip list' output (#​28425, @​joestringer)
  • Remove AWS-CONNMARK-CHAIN iptable rules when running in ENI mode. (#​28676, @​nebril)
  • resource: Fix race condition in handling of Kubernetes object delete event retrying. In the very rare case when an object was created, deleted and re-created with the same name and the handling of the first deletion failed, the handling of delete event may have been retried even though the object was re-created. Only affected features using the Resource-library (LB IPAM, Mutual Auth and ClusterMesh). (#​27340, @​joamaki)
  • srv6: modify h.encap location in the datapath to avoid incompatibility with IPv4Masq (#​28817, @​ldelossa)
  • When the CT entry for a DSR connection is garbage-collected, the corresponding SNAT entry is now also removed. (#​28857, @​julianwiedmann)

CI Changes:

Misc Changes:

Docker Manifests

cilium

docker.io/cilium/cilium:v1.15.0-pre.2@​sha256:7f077c49ce091428b04de006d5f4cb01b8e32d63dc1d45fa3e372d624681e836
quay.io/cilium/cilium:v1.15.0-pre.2@​sha256:7f077c49ce091428b04de006d5f4cb01b8e32d63dc1d45fa3e372d624681e836

clustermesh-apiserver

docker.io/cilium/clustermesh-apiserver:v1.15.0-pre.2@​sha256:19539c7470f27431ee06e4d4bccad40ca206430e3b5f31c8c86cc96e71d85127
quay.io/cilium/clustermesh-apiserver:v1.15.0-pre.2@​sha256:19539c7470f27431ee06e4d4bccad40ca206430e3b5f31c8c86cc96e71d85127

docker-plugin

docker.io/cilium/docker-plugin:v1.15.0-pre.2@​sha256:033f762410bee062c47df96313ffda60683f682db8b562d81614fa7130d3b643
quay.io/cilium/docker-plugin:v1.15.0-pre.2@​sha256:033f762410bee062c47df96313ffda60683f682db8b562d81614fa7130d3b643

hubble-relay

docker.io/cilium/hubble-relay:v1.15.0-pre.2@​sha256:74b20caf534472e274eb020e8ceaf4abfe8d6540c282cb648eb4e0420bccf782
quay.io/cilium/hubble-relay:v1.15.0-pre.2@​sha256:74b20caf534472e274eb020e8ceaf4abfe8d6540c282cb648eb4e0420bccf782

kvstoremesh

docker.io/cilium/kvstoremesh:v1.15.0-pre.2@​sha256:68906ec4ff4577eeaff3a263a68037aae83f6727437e07958c6f7b2cac6b564b
quay.io/cilium/kvstoremesh:v1.15.0-pre.2@​sha256:68906ec4ff4577eeaff3a263a68037aae83f6727437e07958c6f7b2cac6b564b

operator-alibabacloud

docker.io/cilium/operator-alibabacloud:v1.15.0-pre.2@​sha256:a6ff662a0e07a383bc617579ca9ece9c093386a001582bc7588ab1e5b5fdf92e
quay.io/cilium/operator-alibabacloud:v1.15.0-pre.2@​sha256:a6ff662a0e07a383bc617579ca9ece9c093386a001582bc7588ab1e5b5fdf92e

operator-aws

docker.io/cilium/operator-aws:v1.15.0-pre.2@​sha256:81897d31042f34bac5d0d2a25d6dd64f7f294c5711f39ef47ddcb68ef05c1be0
quay.io/cilium/operator-aws:v1.15.0-pre.2@​sha256:81897d31042f34bac5d0d2a25d6dd64f7f294c5711f39ef47ddcb68ef05c1be0

operator-azure

docker.io/cilium/operator-azure:v1.15.0-pre.2@​sha256:01b92fc10fa76117f61f40fdd20c25d45ea8c205979423e2afd911523317e3ce
quay.io/cilium/operator-azure:v1.15.0-pre.2@​sha256:01b92fc10fa76117f61f40fdd20c25d45ea8c205979423e2afd911523317e3ce

operator-generic

docker.io/cilium/operator-generic:v1.15.0-pre.2@​sha256:e5506ddf0665307cf4012a9fbe3f1a51c722b63a12e7abd357119b7c2d1f68af
quay.io/cilium/operator-generic:v1.15.0-pre.2@​sha256:e5506ddf0665307cf4012a9fbe3f1a51c722b63a12e7abd357119b7c2d1f68af

operator

docker.io/cilium/operator:v1.15.0-pre.2@​sha256:060831c979d9eb636e70a51a1e3e5e6eb9f3297492c35b9c6d502a47c11b901e
quay.io/cilium/operator:v1.15.0-pre.2@​sha256:060831c979d9eb636e70a51a1e3e5e6eb9f3297492c35b9c6d502a47c11b901e


Configuration

📅 Schedule: Branch creation - "on monday" (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 this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Signed-off-by: cilium-renovate[bot] <134692979+cilium-renovate[bot]@users.noreply.github.com>
@cilium-renovate cilium-renovate bot requested a review from a team as a code owner November 6, 2023 12:12
@cilium-renovate cilium-renovate bot added release-blocker This PR or issue is blocking the next release. release-note/dependency This PR updates one or multiple dependencies labels Nov 6, 2023
@mtardy mtardy merged commit a3dba71 into main Nov 6, 2023
31 checks passed
@mtardy mtardy deleted the renovate/patch-all-k8s-pkg-go-deps-main branch November 6, 2023 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blocker This PR or issue is blocking the next release. release-note/dependency This PR updates one or multiple dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant