Skip to content

Conversation

JJGadgets
Copy link
Contributor

@JJGadgets JJGadgets commented Aug 13, 2025

Please ensure your pull request adheres to the following guidelines:

  • For first time contributors, read Submitting a pull request
  • All code is covered by unit and/or runtime tests where feasible.
  • All commits contain a well written commit description including a title,
    description and a Fixes: #XXX line if the commit addresses a particular
    GitHub issue.
  • If your commit description contains a Fixes: <commit-id> tag, then
    please add the commit author[s] as reviewer[s] to this issue.
  • All commits are signed off. See the section Developer’s Certificate of Origin
  • Provide a title or release-note blurb suitable for the release notes.
  • Are you a user of Cilium? Please add yourself to the Users doc
  • Thanks for contributing!

Pass the api-server-urls Helm value as a container args to the config initContainer of the cilium-agent DaemonSet.

This will allow the config initContainer to hit apiserver correctly to build the rest of the config.

Fixes #41108

Fix agent config initContainer unable to hit apiservers in apiServerURLs by passing as container arg

@JJGadgets JJGadgets requested review from a team as code owners August 13, 2025 10:49
@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Aug 13, 2025
@github-actions github-actions bot added the kind/community-contribution This was a contribution made by a community member. label Aug 13, 2025
Pass the api-server-urls Helm value as a container args to the config initContainer of the cilium-agent DaemonSet.

This will allow the config initContainer to hit apiserver correctly to build the rest of the config.

Fixes cilium#41108

Signed-off-by: JJGadgets <git@jjgadgets.tech>
@gandro
Copy link
Member

gandro commented Aug 13, 2025

Requesting a review from @aditighag

Copy link
Member

@gandro gandro left a comment

Choose a reason for hiding this comment

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

Helm-wise this looks okay to me.

@gandro gandro added release-note/bug This PR fixes an issue in a previous release of Cilium. needs-backport/1.18 This PR / issue needs backporting to the v1.18 branch labels Aug 13, 2025
@maintainer-s-little-helper maintainer-s-little-helper bot removed dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. labels Aug 13, 2025
@gandro gandro added area/helm Impacts helm charts and user deployment experience dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. labels Aug 13, 2025
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Aug 13, 2025
@JJGadgets
Copy link
Contributor Author

@gandro errrr so does it need a revision to the release note label...?

The initial PR didn't have it, but I've since added it after seeing the bot label, so I'm not sure if it's fine as is, or it needs changes and you're just fighting the bot.

@gandro
Copy link
Member

gandro commented Aug 13, 2025

@gandro errrr so does it need a revision to the release note label...?

The initial PR didn't have it, but I've since added it after seeing the bot label, so I'm not sure if it's fine as is, or it needs changes and you're just fighting the bot.

I think there was some kind of race condition on GitHub's side. I think the GitHub UI re-added the "dont-merge" label when I added the "area/helm" label as I likely still the "dont-merge" label on the PR locally. I think everything should be fine now, since the bot corrected the superfluous label.

Copy link
Member

@aditighag aditighag left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution - LGTM! 🚀

@aditighag
Copy link
Member

/test

@gandro gandro enabled auto-merge August 14, 2025 07:07
@JJGadgets
Copy link
Contributor Author

@gandro @aditighag Is there a way to resolve the checks that are failing so the automerge goes through? I'm not sure how to continue from here.

@gandro
Copy link
Member

gandro commented Aug 18, 2025

I've restarted them. They look like unrelated flakes

@gandro gandro added this pull request to the merge queue Aug 18, 2025
Merged via the queue into cilium:main with commit 8d1da44 Aug 18, 2025
68 of 74 checks passed
@joamaki joamaki mentioned this pull request Aug 19, 2025
19 tasks
@joamaki joamaki added backport-pending/1.18 The backport for Cilium 1.18.x for this PR is in progress. and removed needs-backport/1.18 This PR / issue needs backporting to the v1.18 branch labels Aug 19, 2025
@github-actions github-actions bot added backport-done/1.18 The backport for Cilium 1.18.x for this PR is done. and removed backport-pending/1.18 The backport for Cilium 1.18.x for this PR is in progress. labels Aug 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm Impacts helm charts and user deployment experience backport-done/1.18 The backport for Cilium 1.18.x for this PR is done. kind/community-contribution This was a contribution made by a community member. release-note/bug This PR fixes an issue in a previous release of Cilium.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

New api-server-urls flag should be added as args to config initContainer
4 participants