Skip to main content
In this lesson, we explore how to enforce multi-tenancy in Kubernetes by applying network policies. These policies enhance security in multi-tenant clusters by isolating network traffic between different tenants and their applications. This tutorial builds on concepts discussed in the Kubernetes Troubleshooting for Application Developers course and sets the stage for more advanced topics in the Kubernetes Challenges course.

​
Overview of Network Policies

Network policies enable administrators to define rules that control the flow of network traffic between pods in Kubernetes. Key elements of these policies include: • Pod Selectors: Identify target pods based on their labels.
• Namespace Selectors: Specify the namespaces to which the policy applies.
• Ports: Define allowed or restricted port numbers or ranges.
• Protocols: Indicate the applicable protocols, such as TCP or UDP.
Network policies are fundamental to securing multi-tenant environments by ensuring that only authorized communications occur between specified pods and namespaces.

​
Multi-Tenant Use Case

Imagine a Kubernetes cluster with two namespaces: tenant A and tenant B. In this scenario, you may want to restrict traffic between these namespaces. For instance, a policy could allow pods in tenant A (identified by a particular label) to accept TCP traffic on port 8080 only from pods in tenant B.

​
Example: Allowing Inter-Tenant Traffic

Below is an example YAML manifest for a network policy that permits pods labeled with app: backend in the tenant_a namespace to receive TCP traffic on port 8080 from any pod in a namespace labeled as tenant_b: 
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-tenant-a-to-tenant-b
  namespace: tenant_a
spec:
  podSelector:
    matchLabels:
      app: backend
  ingress:
  - from:
    - namespaceSelector:
        matchLabels:
          tenant: tenant_b
  ports:
  - protocol: TCP
    port: 8080
This configuration illustrates how network policies can control and secure inter-tenant communications in a Kubernetes cluster. By setting precise rules for pod and namespace selectors, ports, and protocols, administrators can ensure that only allowed interactions occur.

​
Conclusion

Effective traffic management is critical for the security of multi-tenant Kubernetes clusters. Utilizing network policies enables administrators to maintain granular control over network communications and isolate traffic between tenants. Further exploration of Kubernetes security best practices will enhance your ability to secure your cluster effectively.
For more details on Kubernetes security, visit the Kubernetes Documentation and explore other related resources.

Watch Video