• thockin
  • caseydavenport title: Network Policies

  • TOC {:toc}

A network policy is a specification of how selections of pods are allowed to communicate with each other and other network endpoints.

NetworkPolicy resources use labels to select pods and define whitelist rules which allow traffic to the selected pods in addition to what is allowed by the isolation policy for a given namespace.


You must enable the extensions/v1beta1/networkpolicies runtime config in your apiserver to enable this resource.

You must also be using a networking solution which supports NetworkPolicy - simply creating the resource without a controller to implement it will have no effect.

Configuring Namespace Isolation Policy

Isolation can be configured on a per-namespace basis. Once isolation is configured on a namespace it will be applied to all pods in that namespace. Currently, only isolation policy on inbound traffic (ingress) can be defined.

The following ingress isolation types being supported:

  • DefaultDeny: Pods in the namespace will be inaccessible from any source except the pod's local node.

Ingress isolation can be enabled using an annotation on the Namespace.

kind: Namespace
apiVersion: v1
    net.beta.kubernetes.io/network-policy: |
        "ingress": {
          "isolation": "DefaultDeny"

To configure the annotation via kubectl:

{% raw %}
kubectl annotate ns <namespace> "net.beta.kubernetes.io/network-policy={\"ingress\": {\"isolation\": \"DefaultDeny\"}}"
{% endraw %}

See the NetworkPolicy getting started guide for an example.

The NetworkPolicy Resource

See the api-reference for a full definition of the resource.

A minimal NetworkPolicy might look like this:

apiVersion: extensions/v1beta1
kind: NetworkPolicy
 name: test-network-policy
 namespace: default
    role: db
  - from:
     - namespaceSelector:
         project: myproject
     - podSelector:
         role: frontend
     - protocol: tcp
       port: 6379

POSTing this to the API server will have no effect unless your chosen networking solution supports network policy.

Mandatory Fields: As with all other Kubernetes config, a NetworkPolicy needs apiVersion, kind, and metadata fields. For general information about working with config files, see here, here, and here.

spec: NetworkPolicy spec has all the information needed to define a network isolation policy in the deployed controller.

podSelector: Each NetworkPolicy includes a podSelector which selects the grouping of pods to which the ingress rules in the policy apply.

ingress: Each NetworkPolicy includes a list of whitelist ingress rules. Each rule allows traffic which matches both the from and ports sections.

This example NetworkPolicy has the following characteristics:

  1. applies to all pods in the default namespace with the label "role=db"
  2. allows tcp/6379 ingress traffic to the "role=db" pods from any pod in the current namespace with the label "role=frontend" (due to the podSelector list element)
  3. allows tcp/6379 ingress traffic to the "role=db" pods from any pod in the namespace "myproject" (due to the namespaceSelector list element)