-
Notifications
You must be signed in to change notification settings - Fork 3.4k
helm: fix duplicate configmap key for bpf-lb-sock-terminate-pod-connections
#35703
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
helm: fix duplicate configmap key for bpf-lb-sock-terminate-pod-connections
#35703
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM from sig-k8s.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall. One minor question
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the change! Could you squash your commits into one with git rebase
? Other than that this PR should then be good to go.
…ections` Previously, when both `socketLB.enabled` and `socketLB.terminatePodConnections`were set in the Helm chart, the cilium-configmap would include the `bpf-lb-sock-terminate-pod-connections` twice. This fixes the issue by only emitting the key once. Signed-off-by: Fred Heinecke <fred.heinecke@yahoo.com>
b270f55
to
727d0b4
Compare
Sure - done. |
/test |
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: <commit-id>
tag, thenplease add the commit author[s] as reviewer[s] to this issue.
Previously, when both
socketLB.enabled
andsocketLB.terminatePodConnections
were set in the Helm chart, the cilium-configmap would include thebpf-lb-sock-terminate-pod-connections
twice. This fixes the issue by only emitting the key once.This issue appears to affect Flux CD HelmReleases, but not Helmfile for some reason. I think Flux renders the Helm chart internally prior to sending the manifests to the API server, whereas Helmfile invokes
helm
, which appears to remove or otherwise merge duplicate keys.