2V0-71.23 Question 100
Select 3An organization is using VMware Tanzu Kubernetes Grid (TKG) and has deployed the Contour ingress controller to manage traffic into its Kubernetes clusters. The team notices that some applications require external HTTPS access, while others need to route traffic based on specific HTTP headers. Which of the following are capabilities of the Contour ingress controller that can address these requirements?
- A
Contour supports HTTPS termination to enable secure external access for applications.
- B
Contour can route traffic based on specific HTTP headers using advanced routing rules.
- C
Contour provides built-in policies for automatic scaling of Kubernetes pods.
- D
Contour integrates with Envoy as the data plane for high-performance Layer 7 traffic management.
- E
Contour can serve as a storage backend for persistent volume claims in Kubernetes.
Show answer and explanation
Correct answers: A, B, D
Explanation
The Contour ingress controller is designed to manage application-layer traffic in Kubernetes environments. It supports HTTPS termination for secure external access, advanced routing rules such as header-based routing, and leverages Envoy as its data plane for high-performance traffic management. However, it does not handle pod scaling or act as a storage backend, as these are outside the scope of an ingress controller's functionality.
- A. Correct.
Correct. Contour supports HTTPS termination by utilizing TLS configurations, enabling secure external access for applications deployed in Kubernetes.
- B. Correct.
Correct. Contour allows the configuration of advanced routing rules, including HTTP header-based routing, making it possible to route traffic based on specific headers.
- C. Incorrect.
Incorrect. Contour does not manage the automatic scaling of Kubernetes pods; this functionality is typically handled by Kubernetes itself or other tools like the Horizontal Pod Autoscaler.
- D. Correct.
Correct. Contour integrates with Envoy as its data plane, leveraging Envoy's high-performance capabilities for Layer 7 (application layer) traffic management.
- E. Incorrect.
Incorrect. Contour is not designed to serve as a storage backend for persistent volume claims in Kubernetes; it is an ingress controller focused on traffic routing and management.