chore(deps): update dependency cilium/cilium to v1.14.0 #52
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:
v1.13.4
->v1.14.0
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
cilium/cilium (cilium/cilium)
v1.14.0
: 1.14.0Compare Source
Changelog
The Cilium core team are excited to announce the Cilium 1.14 release. 🎉
Do NOT upgrade to this release if you are using IPsec.
Summary of Changes
Major Changes:
This prevents pods from being scheduled on nodes without Cilium.
The CNI configuration file is no longer removed on agent shutdown.
This means that pod deletion will always succeed; previously it would fail if Cilium was down for an upgrade.
This should help prevent nodes accidentally entering an unmanageable state.
It also means that nodes are not removed from cloud LoadBalancer backends during Cilium upgrades. (#23486, @squeed)
Minor Changes:
CESWriteQPSLimit
toand
CESWriteQPSBurst`.The processed work queue items always trigger a single CES create, update or write request to the kube-apiserver.
The work queue rate limiting effectively limits the rate of writes to the kube-apiserver for CES api objects.
CESWriteQPSLimit
to10
andCESWriteQPSBurst
to20
.50
and burst100
. These values cannot be exceeded regardless of any configuration.CESMaxCEPsInCES
andCESSlicingMode
flags from appearing in logs whenCES
is enabled. (#24675, @dlapcevic)--hubble-monitor-events
flag, to control the event types that get to the hubble subsystem. (#24828, @epk)ingressclass.kubernetes.io/is-default-class
annotation on Cilium's IngressClass (#23719, @meyskens)peerPort
field to CiliumBGPPeeringPolicy for specifying the port of a BGP neighbor. If unspecified, port 179 is used. (#25809, @danehans)--tunnel
in favor of--routing-mode
and--tunnel-protocol
. (#24561, @pchaigno)go_sched_latencies_seconds
(#24745, @derailed)CiliumPodIPPool
resources in multi-pool IPAM mode (#25991, @gandro)ipam.cilium.io/ip-pool
annotation (#25511, @gandro)sec_label
field in remote_endpoint_info structure tosec_identity
(#25057, @ldelossa)enable-endpoint-routes
withenable-high-scale-ipcache
. (#25601, @pchaigno)Bugfixes:
--hubble-monitor-events
logic to be an allowlist (#25167, @epk)toServices
policy where service backend churn left stale CIDR identities (#25687, @christarazi)CI Changes:
MAX_*_OPTIONS
and support for 5.10 (#24122, @pchaigno)Configuration
📅 Schedule: Branch creation - "before 9pm on friday" in timezone Europe/Paris, 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.
This PR has been generated by Mend Renovate. View repository job log here.