Skip to content

v1.18 Backports 2026-01-29#44056

Merged
mhofstetter merged 9 commits intov1.18from
pr/v1.18-backport-2026-01-29-11-27
Jan 30, 2026
Merged

v1.18 Backports 2026-01-29#44056
mhofstetter merged 9 commits intov1.18from
pr/v1.18-backport-2026-01-29-11-27

Conversation

@mhofstetter
Copy link
Copy Markdown
Member

@mhofstetter mhofstetter commented Jan 29, 2026

AritraDey-Dev and others added 3 commits January 29, 2026 11:27
[ upstream commit 5f1ab7e ]

Signed-off-by: Aritra Dey <adey01027@gmail.com>
Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
[ upstream commit 26360b4 ]

Signed-off-by: Aritra Dey <adey01027@gmail.com>
Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
[ upstream commit bfbf498 ]

Fixes: 151d302 ("datapath/tunnel: New flag --underlay-protocol={ipv4,ipv6}")
Signed-off-by: André Martins <andre@cilium.io>
Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
@mhofstetter mhofstetter added kind/backports This PR provides functionality previously merged into master. backport/1.18 This PR represents a backport for Cilium 1.18.x of a PR that was merged to main. labels Jan 29, 2026
@mhofstetter
Copy link
Copy Markdown
Member Author

/test

@mhofstetter mhofstetter marked this pull request as ready for review January 29, 2026 11:25
@mhofstetter mhofstetter requested a review from a team as a code owner January 29, 2026 11:25
@EmilyShepherd
Copy link
Copy Markdown
Contributor

#44042 patch set is appropriate for v1.18 👍

Copy link
Copy Markdown
Member

@MrFreezeex MrFreezeex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! The backport of my PR looks good!

MrFreezeex and others added 6 commits January 30, 2026 09:03
[ upstream commit e382a33 ]

This add back a check to skip some endpoints that should not receive any
traffic in the ClusterMesh context.

Before the fixed commit this filtering was done through the resource /
ParseEndpointSliceV1 but this was removed so that everything can be kept it in
the backend maps while the backends not supposed to serve new connections would
be excluded directly by the datapath.

However as ClusterMesh doesn't retain any info on the Endpoint
conditions, those are essentially lost and we would propagate them like any
fully ready backends unfortunately.

Fixes: 6f41c98 ("loadbalancer: Keep non-serving terminating backends")

Signed-off-by: Arthur Outhenin-Chalandre <git@mrfreezeex.fr>
Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
[ upstream commit 1a1a57e ]

Our current drivers are matched on everything inside install/kubernetes.
When you do `git merge ...`, git will check the return value of any
matching drivers.
In the case of the install/k8s dir we have the kubernetes-update driver.
However, because this presumably completes and returns 0, this also
papers over any legitimate conflicts.

For example, if there is a conflict in cilium/values.yaml that
requires regenerating, but also a legitimate conflict in another
(non-generated) file then this will silently run the kubernetes-update
driver commands and silently skip incoming changes for other files.

This commit tries to make that matching more specific, by matching
only on files we know get overwritten by code generation we avoid
wrongly auto-merging other changes.

Signed-off-by: Tom Hadlaw <tom.hadlaw@isovalent.com>
Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
[ upstream commit 0a67a9d ]

go.mod is not generated, therefore the go mod resolution driver
won't correctly fix merge conflicts. This removes that line
and leaves the auto merge driver to just match the go.sum/vendor files.

Signed-off-by: Tom Hadlaw <tom.hadlaw@isovalent.com>
Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
[ upstream commit 53f4474 ]

Similar to previous commits we avoid bad auto merges as
well as reducing redundant code generation runs by matching
individual api types with specific merge drivers that only
run make generate-x-api commands relevant to the directory.

Previously we would always run make-generate-apis multiple times
which alongside performing incorrect auto-merges also takes a long
time to complete.

Signed-off-by: Tom Hadlaw <tom.hadlaw@isovalent.com>
Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
[ upstream commit 4e7ec78 ]

When running cilium on kernels that were not compiled with
`CONFIG_BPF_EVENTS=y`, no events are passed from BPF back to
userspace, making hubble show no L3/L4 events, without error.

Resolves #37480

Signed-off-by: Emily Shepherd <emily@redcoat.dev>
Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
[ upstream commit b76f928 ]

Signed-off-by: SeungJu Cheon <suunj1331@gmail.com>
Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
@mhofstetter mhofstetter force-pushed the pr/v1.18-backport-2026-01-29-11-27 branch from a1ffade to 1ee21e3 Compare January 30, 2026 08:04
@mhofstetter
Copy link
Copy Markdown
Member Author

/test

@maintainer-s-little-helper maintainer-s-little-helper bot added ready-to-merge This PR has passed all tests and received consensus from code owners to merge. labels Jan 30, 2026
@mhofstetter mhofstetter added this pull request to the merge queue Jan 30, 2026
Merged via the queue into v1.18 with commit 3fb6011 Jan 30, 2026
385 of 391 checks passed
@mhofstetter mhofstetter deleted the pr/v1.18-backport-2026-01-29-11-27 branch January 30, 2026 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/1.18 This PR represents a backport for Cilium 1.18.x of a PR that was merged to main. kind/backports This PR provides functionality previously merged into master. ready-to-merge This PR has passed all tests and received consensus from code owners to merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants