Why Kubernetes on Azure: Tigera-Microsoft Partnership
•Download as PPTX, PDF•
1 like•275 views
How Tigera and Microsoft are collaborating to deliver container network security in Azure Kubernetes Service (AKS)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Why Kubernetes on Azure: Tigera-Microsoft Partnership
Similar to Why Kubernetes on Azure: Tigera-Microsoft Partnership (20)
More from Andrew Randall
More from Andrew Randall (9)
Recently uploaded
Recently uploaded (20)
Why Kubernetes on Azure: Tigera-Microsoft Partnership
- 3. 25x shorter lifetime 10x workloads 900x start time 250x network churn 10x attack surface area
- 6. apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: my-network-policy namespace: my-namespace spec: podSelector: matchLabels: role: db ingress: - from: - podSelector: matchLabels: role: frontend ports: - protocol: TCP port: 6379 Role: db Role: db role: db role: frontend role: helper TCP 6379 role: frontend
- 7. apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: my-network-policy namespace: my-namespace spec: podSelector: matchLabels: role: db ingress: - from: - podSelector: matchLabels: role: frontend ports: - protocol: TCP port: 6379 Role: db Role: db role: db role: frontend role: helper TCP 6379 role: frontend
- 8. apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: my-network-policy namespace: my-namespace spec: podSelector: matchLabels: role: db ingress: - from: - podSelector: matchLabels: role: frontend ports: - protocol: TCP port: 6379 Role: db Role: db role: db role: frontend role: helper TCP 6379 role: frontend
- 9. apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: my-network-policy namespace: my-namespace spec: podSelector: matchLabels: role: db ingress: - from: - podSelector: matchLabels: role: frontend ports: - protocol: TCP port: 6379 Role: db Role: db role: db role: frontend role: helper TCP 6379 role: frontend
- 10. apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: my-network-policy namespace: my-namespace spec: podSelector: matchLabels: role: db ingress: - from: - podSelector: matchLabels: role: frontend ports: - protocol: TCP port: 6379 Role: db Role: db role: db role: frontend role: helper TCP 6379 role: frontend