-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Confusing wording in "Declare Network Policy" task page #49847
Comments
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/retitle Confusing working in "Declare Network Policy" task page |
How about "Define a network policy that applies to the workload"? |
That would be okay. The YAML text shown above the headline is the definition of the Network Policy, so I think changing the confusing headline is needed, especially to remove words "service" and "assign". This is the confusing headline to be replaced: BAD: Good replacements might be: BETTER OPTIONS: Your suggestion: |
"Apply the Network Policy to Pods" would be a better option. |
We are applying a Network Policy to Pods, not a Service. This heading will eliminate any confusion and accurately describes the action. |
/retitle Confusing wording in "Declare Network Policy" task page |
I agree with @dhairya-seth who say:
Thanks everyone..I do not collaborate on GitHub docs often, your patience is appreciated! |
Suggestion about confusing wording, in particular, this line on page at k8s.io/docs/tasks/administer-cluster/declare-network-policy/ :
I have two problems with that:
NOTICE: I am not a kubernetes expert! Just really enjoying the excellent documentation, thanks!!!
Page: https://k8s.io/docs/tasks/administer-cluster/declare-network-policy/
The text was updated successfully, but these errors were encountered: