Skip to content

Network Policies ​

Learn about the network policies for the SAP BTP Operator module and how to manage them.

Default Network Policies ​

To increase security, the SAP BTP Operator module creates the following network policies that control traffic to and from its Pods:

  • kyma-project.io--btp-operator-allow-to-apiserver: Allows egress from the SAP BTP Operator module Pods to any destination on TCP port 443 (for example, Kubernetes API server)
  • kyma-project.io--btp-operator-to-dns: Allows egress from the SAP BTP Operator module Pods to DNS services (UDP/TCP port 53, 8053) for cluster and external DNS resolution
  • kyma-project.io--allow-btp-operator-metrics: Allows ingress to the SAP BTP Operator module Pods on TCP port 8080 from Pods labeled networking.kyma-project.io/metrics-scraping: allowed (metrics scraping)
  • kyma-project.io--btp-operator-allow-to-webhook: Allows ingress to the SAP BTP Operator module Pods on TCP port 9443 (webhook server) from any source

Disable Network Policies ​

To disable network policies for SAP BTP Operator, add the following annotation to the BtpOperator custom resource (CR):

bash
kubectl annotate btpoperators/btpoperator -n kyma-system operator.kyma-project.io/btp-operator-disable-network-policies=true

WARNING

If you disable the network policies, you allow all ingress and egress traffic to and from the module's Pods.

Enable Network Policies ​

To enable network policies, remove the following annotation:

bash
kubectl annotate btpoperators/btpoperator -n kyma-system operator.kyma-project.io/btp-operator-disable-network-policies-

Verify Status ​

To check if the network policies are active, run:

bash
kubectl get networkpolicies -n kyma-system -l kyma-project.io/managed-by=btp-manager