Skip to content

Conversation

pippolo84
Copy link
Member

@pippolo84 pippolo84 commented Jun 26, 2025

Commit f5f831f ("cilium, helm: Fix hostPort and externalIPs"), backported to v1.17 in #37126, removed the individual setting for externalIPs and hostPort when KPR is disabled, but left them for KPR="partial" that has been deprecated in v1.14 (see #26036).
This backport fixes that removing nodePort and externalIPs but also all the other stale occurrences of the "partial" value and "disabled" value for KPR in helm.

Fixes: #40073

Once this PR is merged, a GitHub action will update the labels of these PRs:

 39721

brb added 3 commits June 26, 2025 12:31
[ upstream commit 6f33115 ]

[ backporter's notes: Fixed minor conflicts in values.schema.json due to
externalWorkloads removed in main branch. ]

The commit f5f831f ("cilium, helm: Fix hostPort and externalIPs")
removed the individual setting of each flag when --kpr=false:

  If KPR is false, setting these to true does not make any sense. Thus,
  remove this to avoid confusion.

However, it kept "partial", which is removed since v1.14 [1] (EOL).

Remove the options entirely.

[1]: #26036

Signed-off-by: Martynas Pumputis <martynas@isovalent.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
[ upstream commit 8d1884a ]

It was removed in v1.14 [1] (EOL)

[1]: #26036

Signed-off-by: Martynas Pumputis <martynas@isovalent.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
[ upstream commit 40c6f00 ]

The "disabled" value is deprecated since v1.14 (EOL). Change the check
to == "true" to make the assignment effective.

Signed-off-by: Martynas Pumputis <martynas@isovalent.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
@pippolo84 pippolo84 added kind/backports This PR provides functionality previously merged into master. backport/1.17 This PR represents a backport for Cilium 1.17.x of a PR that was merged to main. labels Jun 26, 2025
@pippolo84 pippolo84 requested a review from brb June 26, 2025 10:34
@pippolo84 pippolo84 marked this pull request as ready for review June 26, 2025 10:42
@pippolo84 pippolo84 requested a review from a team as a code owner June 26, 2025 10:42
@pippolo84
Copy link
Member Author

/test

Copy link
Member

@brb brb left a comment

Choose a reason for hiding this comment

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

Grazie!

@pippolo84 pippolo84 enabled auto-merge June 30, 2025 13:46
@pippolo84 pippolo84 added this pull request to the merge queue Jun 30, 2025
Merged via the queue into v1.17 with commit 96da2ca Jun 30, 2025
445 of 449 checks passed
@pippolo84 pippolo84 deleted the pr/v1.17-backport-2025-06-26-12-22 branch June 30, 2025 14:25
@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 Jun 30, 2025
brb added a commit that referenced this pull request Jul 11, 2025
The [1] commit removed the hostPort.enabled too early. It will be no
longer possible to enable each individual KPR flag only in v1.19. So,
before that we need to support enabling HostPort when KPR=false.

[1] got backported to v1.17 by #40222 to fix [2].

NB: we did not restore externalIPs.enabled, because it is no-op when
KPR=false, and it is implicitly enabled when nodePort.enabled is true.

[1]: 88d1e70
[2]: #40073

Signed-off-by: Martynas Pumputis <martynas@isovalent.com>
brb added a commit that referenced this pull request Jul 11, 2025
The [1] commit removed the hostPort.enabled too early. It will be no
longer possible to enable each individual KPR flag only in v1.19. So,
before that we need to support enabling HostPort when KPR=false.

[1] got backported to v1.17 by #40222 to fix [2].

NB: we did not restore externalIPs.enabled, because it is no-op when
KPR=false, and it is implicitly enabled when nodePort.enabled is true.

[1]: 88d1e70
[2]: #40073

Signed-off-by: Martynas Pumputis <martynas@isovalent.com>
brb added a commit that referenced this pull request Jul 11, 2025
The [1] commit removed the hostPort.enabled too early. It will be no
longer possible to enable each individual KPR flag only in v1.19. So,
before that we need to support enabling HostPort when KPR=false.

[1] got backported to v1.17 by #40222 to fix [2].

NB: we did not restore externalIPs.enabled, because it is no-op when
KPR=false, and it is implicitly enabled when nodePort.enabled is true.

[1]: 88d1e70
[2]: #40073

Signed-off-by: Martynas Pumputis <martynas@isovalent.com>
github-merge-queue bot pushed a commit that referenced this pull request Jul 14, 2025
The [1] commit removed the hostPort.enabled too early. It will be no
longer possible to enable each individual KPR flag only in v1.19. So,
before that we need to support enabling HostPort when KPR=false.

[1] got backported to v1.17 by #40222 to fix [2].

NB: we did not restore externalIPs.enabled, because it is no-op when
KPR=false, and it is implicitly enabled when nodePort.enabled is true.

[1]: 88d1e70
[2]: #40073

Signed-off-by: Martynas Pumputis <martynas@isovalent.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.17 This PR represents a backport for Cilium 1.17.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.

2 participants