From 1f6a98d13451bb13c32da65578db556f1e3070d5 Mon Sep 17 00:00:00 2001 From: Ahmet Alp Balkan Date: Thu, 29 Jun 2017 21:49:53 -0700 Subject: [PATCH] Use correct apigroup for NetworkPolicy Follow-up to #4225. networking -> networking.k8s.io. Signed-off-by: Ahmet Alp Balkan --- docs/concepts/services-networking/network-policies.md | 4 ++-- docs/tasks/administer-cluster/declare-network-policy.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/concepts/services-networking/network-policies.md b/docs/concepts/services-networking/network-policies.md index f66944b64c..83c21b4ac9 100644 --- a/docs/concepts/services-networking/network-policies.md +++ b/docs/concepts/services-networking/network-policies.md @@ -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 diff --git a/docs/tasks/administer-cluster/declare-network-policy.md b/docs/tasks/administer-cluster/declare-network-policy.md index 8bd4f26c48..1f5e18634b 100644 --- a/docs/tasks/administer-cluster/declare-network-policy.md +++ b/docs/tasks/administer-cluster/declare-network-policy.md @@ -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: