Advanced Kubernetes/AKS Network & Infrastructure

For an AKS cluster, there are two varieties of site visitors. First one is the inner site visitors between pods. The second is the ingress and egress site visitors that’s between pods and the top customers or the web.

This course gives the instruments and strategies to safe these networks utilizing instruments like Community Insurance policies with Calico, TLS certificates, and many others.

Microsoft gives the next suggestions to safe an AKS cluster and this course will attempt to go deeper with demonstration.

Advice 1: To distribute HTTP or HTTPS site visitors to your purposes, use ingress assets and controllers. In comparison with an Azure load balancer, ingress controllers present additional options and may be managed as native Kubernetes assets.

Advice 2: To scan incoming site visitors for potential assaults, use an online utility firewall (WAF) equivalent to Barracuda WAF for Azure or Azure Software Gateway. These extra superior community assets can even route site visitors past simply HTTP and HTTPS connections or fundamental TLS termination.

Advice 3: Use community insurance policies to permit or deny site visitors to pods. By default, all site visitors is allowed between pods inside a cluster. For improved safety, outline guidelines that restrict pod communication.

Advice 4: Don’t expose distant connectivity to your AKS nodes. Create a bastion host, or bounce field, in a administration digital community. Use the bastion host to securely route site visitors into your AKS cluster to distant administration duties.