-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
doc: fixes markdown in hostnet policy troubleshooting #13146
doc: fixes markdown in hostnet policy troubleshooting #13146
Conversation
Signed-off-by: Jed Salazar jed@isovalent.com
Documentation/policy/language.rst
Outdated
@@ -1124,7 +1124,7 @@ is labeled correctly in your environment. In the example configuration, you can | |||
run ``kubectl get nodes -o wide|grep type=ingress-worker`` to verify labels | |||
match the policy. | |||
|
|||
You can verify the policy was properly parsed and applied by ``exec``ing into | |||
You can verify the policy was applied by running ``kubectl exec`` in |
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.
This new wording can be read as "run kubectl inside the cilium agent pod", which doesn't make sense since kubectl isn't available there. Is it important for us to even mention execing or pods here or just say "Run cilium policy get..."?
If we think this should still be here, maybe we can clarify the wording a bit more, such as:
You can verify the policy was applied by running ``kubectl exec`` in | |
You can verify the policy was applied by running ``kubectl exec -n $CILIUM_NAMESPACE cilium-xxxx cilium policy get`` for the cilium pod ... |
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 changed the wording to be more clear per your suggestion but I'm open to making further changes. I was intending to assume no prior knowledge so I included the exec command in full in your example. Let me know if I should revert to something simpler.
Signed-off-by: Jed Salazar jed@isovalent.com
Signed-off-by: Jed Salazar jed@isovalent.com