Skip to content

Latest commit

 

History

History
26 lines (22 loc) · 1.75 KB

shoot_network_policies.md

File metadata and controls

26 lines (22 loc) · 1.75 KB
Raw

Network policies in the Shoot Cluster

In addition to deploying network policies into the Seed, Gardener deploys network policies into the kube-system namespace of the Shoot. These network policies are used by Shoot system components (that are not part of the control plane). Other namespaces in the Shoot do not contain network policies deployed by Gardener.

As best practice, every pod deployed into the kube-system namespace should use appropriate network policies in order to only allow required network traffic. Therefore, pods should have labels matching to the selectors of the available network policies.

Gardener deploys the following network policies:

NAME                                       POD-SELECTOR                                   
gardener.cloud--allow-from-seed            networking.gardener.cloud/from-seed=allowed            
gardener.cloud--allow-to-apiserver         networking.gardener.cloud/to-apiserver=allowed         
gardener.cloud--allow-to-dns               networking.gardener.cloud/to-dns=allowed               
gardener.cloud--allow-to-from-nginx        app=nginx-ingress                                      
gardener.cloud--allow-to-kubelet           networking.gardener.cloud/to-kubelet=allowed           
gardener.cloud--allow-to-public-networks   networking.gardener.cloud/to-public-networks=allowed

Additionally, there can be network policies deployed by Gardener extensions such as extension-calico.

NAME                                       POD-SELECTOR  
gardener.cloud--allow-from-calico-node     k8s-app=calico-typha