QuestionQ13

VerifiedConfiguring managed network services

You manage a containerized application environment on Google Kubernetes Engine (GKE). You deployed a microservice using a Kubernetes Service manifest that defines a named port, http-api, for its primary endpoint. You are now configuring an external HTTP(S) load balancer to expose this microservice. You must ensure that the configuration is independent of the actual port number and follows best practices.

What should you do?

Explanation

GKE container-native load balancing uses GCE_VM_IP_PORT NEGs containing Pod endpoints, avoiding the additional NodePort and kube-proxy hops of instance-group backends. An Ingress backend can reference the Kubernetes Service port by its name, such as http-api, rather than a numeric port. Compute Engine backend-service named ports apply only to instance-group backends, not GCE_VM_IP_PORT NEGs.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!