kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Use correct apigroup for NetworkPolicy 

Follow-up to #4225. networking -> networking.k8s.io.

Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
This commit is contained in:
Ahmet Alp Balkan 2017-06-29 21:49:53 -07:00
parent ac5c52f860
commit 1f6a98d134
No known key found for this signature in database
GPG Key ID: 5C02521D7B216AD6
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/concepts/services-networking/network-policies.md
View File

@ -78,7 +78,7 @@ See the [NetworkPolicy getting started guide](/docs/getting-started-guides/netwo
You can create a "default" isolation policy for a Namespace by creating a NetworkPolicy that selects all pods but does not allow any traffic:
```yaml
apiVersion: networking/v1
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default-deny
@ -91,7 +91,7 @@ This ensures that even pods that aren't selected by any other NetworkPolicy will
Alternatively, if you want to allow all traffic for all pods in a Namespace (even if policies are added that cause some pods to be treated as "isolated"), you can create a policy that explicitly allows all traffic:
```yaml
apiVersion: networking/v1
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-all

2
docs/tasks/administer-cluster/declare-network-policy.md
View File

@ -73,7 +73,7 @@ Let's say you want to limit access to the `nginx` service so that only pods with
```yaml
kind: NetworkPolicy
apiVersion: networking/v1
apiVersion: networking.k8s.io/v1
metadata:
name: access-nginx
spec: