Skip to content
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

Update network-policies.md #17335

Merged
merged 2 commits into from Nov 4, 2019
Merged

Update network-policies.md #17335

merged 2 commits into from Nov 4, 2019

Conversation

sdarwin
Copy link
Contributor

@sdarwin sdarwin commented Oct 31, 2019

Add explanation of policy evaluation order from kubernetes/kubernetes#75435

@k8s-ci-robot
Copy link
Contributor

Welcome @sdarwin!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 31, 2019
@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language sig/docs Categorizes an issue or PR as relevant to SIG Docs. labels Oct 31, 2019
@netlify
Copy link

netlify bot commented Oct 31, 2019

Deploy preview for kubernetes-io-master-staging ready!

Built with commit a02f9b9

https://deploy-preview-17335--kubernetes-io-master-staging.netlify.com

@bradtopol
Copy link
Contributor

/cc @cmluciano

@bradtopol
Copy link
Contributor

/assign

@bradtopol
Copy link
Contributor

Hi @cmluciano can you serve as a technical reviewer for this? Just add a /lgtm when you feel it is technically correct and I'll take care of the rest. Thanks!

Add explanation of policy evaluation order from kubernetes/kubernetes#75435
@@ -28,6 +28,8 @@ By default, pods are non-isolated; they accept traffic from any source.

Pods become isolated by having a NetworkPolicy that selects them. Once there is any NetworkPolicy in a namespace selecting a particular pod, that pod will reject any connections that are not allowed by any NetworkPolicy. (Other pods in the namespace that are not selected by any NetworkPolicy will continue to accept all traffic.)

Network policies do not conflict, they are additive. If policies select a pod, the pod is restricted to what is allowed by the union of those policies' ingress/egress rules. Thus, order of evaluation does not affect the policy result.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

really nit: "If any policy selects a pod"

Copy link
Contributor Author

@sdarwin sdarwin Nov 1, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just in this context, "If policies select a pod" could be worded "If multiple policies select a pod" , since it's about explaining that situation, of multiple policies/rules, rather than the case of a single policy.

@thockin
Copy link
Member

thockin commented Nov 1, 2019 via email

@sdarwin
Copy link
Contributor Author

sdarwin commented Nov 1, 2019

The point is that AS SOON as one policy selects a pod, rules apply. Whether that is one, two, or 10 additive policies.

That is certainly true.

The original sentence was copied verbatim from kubernetes/kubernetes#75435

An issue is that later in the sentences it refers back to "those policies'" which is plural. If the first part of the sentence switches to singular such as "if any (one) policy", then the later part should switch too.

Example updates:

choice 1: "If any policy selects a pod, the pod is restricted to what is allowed by the union of all applicable policies' ingress/egress rules."

choice 2: "If any policy or policies select a pod, the pod is restricted to what is allowed by the union of all those policies' ingress/egress rules."

perhaps choice 2?

@thockin
Copy link
Member

thockin commented Nov 1, 2019 via email

Copy link
Contributor

@cmluciano cmluciano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes look good per Tim’s comments

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 4, 2019
@makoscafee
Copy link
Contributor

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: makoscafee

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 4, 2019
@k8s-ci-robot k8s-ci-robot merged commit 4450206 into kubernetes:master Nov 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants