All Products
Search
Document Center

Container Service for Kubernetes:FAQ about network management

Last Updated:Mar 19, 2024

This topic provides answers to some frequently asked questions about container networks, Services, Ingresses, and DNS.

Table of contents

FAQ about container networks

FAQ about Terway

FAQ about Flannel

FAQ about kube-proxy

FAQ about IPv6

How do I fix common issues related to IPv4/IPv6 dual stack?

Other issues

Service FAQ

FAQ about Server Load Balancer (SLB)

FAQ about updates of the cloud controller manager (CCM)

FAQ about using existing SLB instances

Other issues

What do I do if errors occur in Services?

How do I configure listeners for a NodePort Service?

How do I access a NodePort Service?

How do I configure a proper node port range?

How is session persistence implemented in Kubernetes Services?

Ingress FAQ

FAQ about Ingress configurations

FAQ about connectivity

FAQ about canary releases

FAQ about errors

FAQ about other issues

DNS FAQ

What do I do if I cannot access a CoreDNS pod by running the exec command?

FAQ about network configurations

How do I access cluster workloads over the Internet?

Container Service for Kubernetes (ACK) allows you to use the following methods to access workloads over the Internet:

How do I configure the pods to obtain the real IP addresses of clients?

  • If Web Application Firewall (WAF) is used and your cluster uses SLB instances to provide external services, set externaltrafficpolicy to Local for the Services that are used to expose the pods. This way, you can obtain the real IP addresses of clients. If your cluster uses Ingresses to provide external services, set externaltrafficpolicy to Local for the nginx-ingress-lb Service.

  • For more information about WAF, see Use WAF or transparent WAF.