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
Correct Istio Integration Documentation for Cilium CLI Flag Usage #30152
Conversation
Signed-off-by: Jimmy Song <rootsongjc@gmail.com>
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 a lot for this! Please find some suggestions below.
Signed-off-by: Jimmy Song <rootsongjc@gmail.com>
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!
/test |
Commit 6be911f does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
Commit 92640e1 does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
I recently followed the instructions in the Cilium Documentation for installing Istio alongside Cilium. The documentation suggests using the
--config bpf-lb-sock-hostns-only=true
CLI flag with Cilium to ensure compatibility with Istio. However, I noticed that the cilium CLI does not have a --config flag. Instead, it appears that the correct usage should be--set socketLB.hostNamespaceOnly=true
.I know that the
cilium
CLI in the Cilium Agent has the--config
flag, but in the context of this document, I think the one to use would be the Cilium Installation CLI.