-
Notifications
You must be signed in to change notification settings - Fork 3.2k
nonMasqueradeCIDRs configuration added to the helm chart #20137
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
Conversation
d01e143
to
7cf5e5e
Compare
install/kubernetes/cilium/templates/cilium-agent/daemonset.yaml
Outdated
Show resolved
Hide resolved
bd89b2a
to
ff20223
Compare
I'm a bit confused what the core proposal is here. I suspect we just need some documentation about how to use the feature, not Helm changes. I believe you should be able to do:
And then create a new ConfigMap in
If we put this into the Helm charts, then my concern is that users who use this feature and upgrade will have their settings overwritten. I'm not sure if it even makes sense for Cilium's Helm configuration to control this configmap? |
One option is that we could include an example copy of this configmap in |
@joestringer the specific use-case I have is to eliminate a separate manifest for the configmap that isn't tied to a deployment. Having all of ciliums components managed through a single flux helmdeployment would simplify my deployment repo a bit. I think wrapping the whole configmap in an if statement, and leaving .Values.ipMasqAgent.config commented out would keep existing functionality the same. Then by default it's managed separately as it is now, but can be created with the helm chart. something like {{- if and .Values.ipMasqAgent .Values.ipMasqAgent.enabled .Values.ipMasqAgent.config }}
apiVersion: v1
kind: ConfigMap
metadata:
name: ip-masq-agent
namespace: {{ .Release.Namespace }}
data:
config: |
{{ toJson .Values.ipMasqAgent.config | indent 4 }}
{{- end }} It's not a huge deal, but could make things a bit nicer. |
I'm sorry for not replying for a long time, I've been busy with work these days.. |
ff20223
to
8a95074
Compare
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.
Could you extend Documentation/concepts/networking/masquerading.rst
to show how to use the new way of configuring the ipmasq?
8a95074
to
8cfcd37
Compare
Sure! Hi @brb , I'm not a english speaker, so If you could give me some advice for new changes, I would be very grateful! |
8cfcd37
to
d7d37ea
Compare
@joestringer @brb Thanks for your suggestions. Now all the changes in the PR. I don't think we can delete the configMap directly here, After my testing, the configMap mounted by the agent pod does not changed, so we should use |
5900ca1
to
74301e1
Compare
Yes, you can patch it. Please use |
Okay, Thanks. |
74301e1
to
d272d27
Compare
/test |
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.
Minor comment, other than that Helm related changes LGTM.
d272d27
to
bf01f96
Compare
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 on helm changes, thanks 🥇
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.
Thank you!
Thanks @kaworu @sayboras ,Hi @joestringer , Now this PR can be merge? |
/test |
test/k8s/datapath_configuration.go
Outdated
@@ -463,81 +449,53 @@ var _ = Describe("K8sDatapathConfig", func() { | |||
res.ExpectSuccess() | |||
tmpEchoPodPath = strings.Trim(res.Stdout(), "\n") | |||
kubectl.ExecMiddle(fmt.Sprintf("sed 's/NODE_WITHOUT_CILIUM/%s/' %s > %s", | |||
helpers.GetFirstNodeWithoutCilium(), echoPodPath, tmpEchoPodPath)).ExpectSuccess() | |||
"k8s3", echoPodPath, tmpEchoPodPath)).ExpectSuccess() |
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.
Why this change?
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.
I'm not sure. This change comes from your suggestion. #20137 (comment), Is the CI failure related to this change?
bf01f96
to
64cb665
Compare
@cyclinder Thanks. Could you rebase your code against the latest Cilium's master. It should fix some GH action failures. Once it's done, I will rerun the CI. |
Signed-off-by: cyclinder <qifeng.guo@daocloud.io>
64cb665
to
dffccdf
Compare
Thanks @brb , I've already rebased with the latest master branch. |
/test |
It seems to the CI failures: ConformanceGKE(ci-gke) has no relation with these changes ? |
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!
Signed-off-by: cyclinder qifeng.guo@daocloud.io
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: #20051