diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2016-08-17 23:24:49 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-08-17 23:24:49 -0700 |
| commit | 39310a68ba849c013357951ef10ba8e86bbf3036 (patch) | |
| tree | facb1ad1ccba1c743897f909fe8ecfb2f85535c3 /runtime-client-server.md | |
| parent | bca3dd1f44b2d0e0d6d5470e38e00fa477fe2c10 (diff) | |
| parent | dab3faa4f1f623710f9ea350426cff2921f79118 (diff) | |
Merge pull request #30511 from danwinship/network-policy-docs
Automatic merge from submit-queue
Remove incorrect docs about unset fields in NetworkPolicyPeer
While hammering out the semantics of not-present vs present-but-empty, we appear to have added incorrect clarifications to NetworkPolicyPeer, where the semantics of PodSelector not being present is supposed to be "do what NamespaceSelector" says, not "select no pods", and likewise with NamespaceSelector not being present.
I think it's clearest if we just don't say anything, since we already said "Exactly one of the following must be specified" above. Alternatively we could be redundant and say "(If not provided, then NamespaceSelector must be set.)" or something like that.
@caseydavenport @thockin
Diffstat (limited to 'runtime-client-server.md')
0 files changed, 0 insertions, 0 deletions