All Products
Search
Document Center

Container Service for Kubernetes:Network management FAQ

Last Updated:Mar 26, 2026

This page indexes frequently asked questions about ACK cluster networking, organized by component: container networks, Services, Ingresses, and DNS. It also covers common network configuration tasks.

Where to start

When traffic isn't reaching your workload, check each layer in order — from the inside out:

Client → DNS → Load balancer → Node → Pod
Layer Go to
Pod can't get an IP or is stuck in ContainerCreating Terway FAQ or Flannel FAQ
Service IP unreachable or SLB stuck in Pending SLB FAQ
Ingress returning errors or wrong TLS cert Ingress configurations FAQ or Errors FAQ
DNS resolution failing in cluster DNS FAQ
Need to expose workloads to the internet Network configurations FAQ

Container network FAQ

Terway FAQ

Flannel FAQ

kube-proxy FAQ

IPv6 FAQ

Other issues

Service FAQ

Server Load Balancer (SLB) FAQ

CCM update FAQ

Existing SLB instances FAQ

Other issues

Ingress FAQ

Ingress configurations FAQ

Connectivity FAQ

Canary releases FAQ

Errors FAQ

Other issues

DNS FAQ

Network configurations FAQ

How do I access cluster workloads over the internet?

ACK supports five methods for exposing workloads to the internet:

How do I get the real client IP address in my Pods?

If your cluster uses SLB instances to provide external services and Web Application Firewall (WAF) is enabled, set externaltrafficpolicy to Local on the Services that expose your Pods. For clusters that use Ingress instead, set externaltrafficpolicy to Local on the nginx-ingress-lb Service.

For WAF configuration details, see Use WAF.

How do I throttle traffic for an ACK cluster?

Use Alibaba Cloud Service Mesh (ASM) to apply traffic throttling. ASM protects your backend services against traffic spikes, service overloading, resource exhaustion, and attacks — reducing costs and improving user experience. For details, see Throttling.