Kubernetes policy, advanced tutorial
The Kubernetes NetworkPolicy API allows users to express ingress and egress policies (starting with Kubernetes 1.8.0) to Kubernetes pods
based on labels and ports.
This guide walks through using Kubernetes NetworkPolicy to define more complex network policies.
Requirements​
- A working Kubernetes cluster and access to it using kubectl
- Your Kubernetes nodes have connectivity to the public internet
- You are familiar with Kubernetes NetworkPolicy
Tutorial flow​
- Create the Namespace and Nginx Service
- Deny all ingress traffic
- Allow ingress traffic to Nginx
- Deny all egress traffic
- Allow egress traffic to kube-dns
- Cleanup Namespace
1. Create the namespace and nginx service​
We'll use a new namespace for this guide. Run the following commands to create it and a plain nginx service listening on port 80.
kubectl create ns advanced-policy-demo
kubectl create deployment --namespace=advanced-policy-demo nginx --image=nginx
kubectl expose --namespace=advanced-policy-demo deployment nginx --port=80
Verify access - allowed all ingress and egress​
Open up a second shell session which has kubectl connectivity to the Kubernetes cluster and create a busybox pod to test policy access. This pod will be used throughout this tutorial to test policy access.
kubectl run --namespace=advanced-policy-demo access --rm -ti --image busybox /bin/sh
This should open up a shell session inside the access pod, as shown below.
Waiting for pod advanced-policy-demo/access-472357175-y0m47 to be running, status is Pending, pod ready: false
If you don't see a command prompt, try pressing enter.
/ #
Now from within the busybox "access" pod execute the following command to test access to the nginx service.
wget -q --timeout=5 nginx -O -
It should return the HTML of the nginx welcome page.
Still within the busybox "access" pod, issue the following command to test access to google.com.
wget -q --timeout=5 google.com -O -
It should return the HTML of the google.com home page.
2. Deny all ingress traffic​
Enable ingress isolation on the namespace by deploying a default deny all ingress traffic policy.
kubectl create -f - <<EOF
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default-deny-ingress
namespace: advanced-policy-demo
spec:
podSelector:
matchLabels: {}
policyTypes:
- Ingress
EOF
Verify access - denied all ingress and allowed all egress​
Because all pods in the namespace are now selected, any ingress traffic which is not explicitly allowed by a policy will be denied.
We can see that this is the case by switching over to our "access" pod in the namespace and attempting to access the nginx service.
wget -q --timeout=5 nginx -O -
It should return:
wget: download timed out
Next, try to access google.com.
wget -q --timeout=5 google.com -O -
It should return:
<!doctype html><html itemscope="" item....
We can see that the ingress access to the nginx service is denied while egress access to outbound internet is still allowed.
3. Allow ingress traffic to Nginx​
Run the following to create a NetworkPolicy which allows traffic to nginx pods from any pods in the advanced-policy-demo namespace.
kubectl create -f - <<EOF
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: access-nginx
namespace: advanced-policy-demo
spec:
podSelector:
matchLabels:
app: nginx
ingress:
- from:
- podSelector:
matchLabels: {}
EOF
Verify access - allowed nginx ingress​
Now ingress traffic to nginx will be allowed. We can see that this is the case by switching over to our "access" pod in the namespace and attempting to access the nginx service.
wget -q --timeout=5 nginx -O -
It should return:
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>...
After creating the policy, we can now access the nginx Service.
4. Deny all egress traffic​
Enable egress isolation on the namespace by deploying a default deny all egress traffic policy.
kubectl create -f - <<EOF
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default-deny-egress
namespace: advanced-policy-demo
spec:
podSelector:
matchLabels: {}
policyTypes:
- Egress
EOF
Verify access - denied all egress​
Now any ingress or egress traffic which is not explicitly allowed by a policy will be denied.
We can see that this is the case by switching over to our "access" pod in the
namespace and attempting to nslookup nginx or wget google.com.
nslookup nginx
It should return something like the following.
Server: 10.96.0.10
Address 1: 10.96.0.10
nslookup: can't resolve 'nginx'
Next, try to access google.com.
wget -q --timeout=5 google.com -O -
It should return:
wget: bad address 'google.com'
The nslookup command can take a minute or more to timeout.
5. Allow DNS egress traffic​
Run the following to create a label of name: kube-system on the kube-system namespace and a NetworkPolicy which allows DNS egress traffic
from any pods in the advanced-policy-demo namespace to the kube-system namespace.
kubectl label namespace kube-system name=kube-system
kubectl create -f - <<EOF
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-dns-access
namespace: advanced-policy-demo
spec:
podSelector:
matchLabels: {}
policyTypes:
- Egress
egress:
- to:
- namespaceSelector:
matchLabels:
name: kube-system
ports:
- protocol: UDP
port: 53
EOF
Verify access - allowed DNS access​
Now egress traffic to DNS will be allowed.
We can see that this is the case by switching over to our "access" pod in the namespace and attempting to lookup nginx and google.com.
nslookup nginx
It should return something like the following.
Server: 10.0.0.10
Address 1: 10.0.0.10 kube-dns.kube-system.svc.cluster.local
Next, try to look up google.com.
nslookup google.com
It should return something like the following.
Name: google.com
Address 1: 2607:f8b0:4005:807::200e sfo07s16-in-x0e.1e100.net
Address 2: 216.58.195.78 sfo07s16-in-f14.1e100.net
Even though DNS egress traffic is now working, all other egress traffic from all pods in the advanced-policy-demo namespace is still blocked. Therefore the HTTP egress traffic from the wget calls will still fail.
6. Allow egress traffic to nginx​
Run the following to create a NetworkPolicy which allows egress traffic from any pods in the advanced-policy-demo namespace to pods with labels matching app: nginx in the same namespace.
kubectl create -f - <<EOF
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-egress-to-advance-policy-ns
namespace: advanced-policy-demo
spec:
podSelector:
matchLabels: {}
policyTypes:
- Egress
egress:
- to:
- podSelector:
matchLabels:
app: nginx
EOF
Verify access - allowed egress access to nginx​
We can see that this is the case by switching over to our "access" pod in the
namespace and attempting to access nginx.
wget -q --timeout=5 nginx -O -
It should return the HTML of the nginx welcome page.
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>...
Next, try to retrieve the home page of google.com.
wget -q --timeout=5 google.com -O -
It should return:
wget: download timed out
Access to google.com times out because it can resolve DNS but has no egress access to anything other than pods with labels matching app: nginx in the advanced-policy-demo namespace.
7. Clean up namespace
You can clean up after this tutorial by deleting the advanced policy demo namespace.
kubectl delete ns advanced-policy-demo