2V0-71.23 Question 294
Select 3An organization is running a Kubernetes cluster managed by VMware Tanzu. They have deployed a microservices-based application and want to ensure it scales automatically based on workload demands. Which of the following methods can be used to implement application autoscaling in this scenario?
- A
Use the Kubernetes Horizontal Pod Autoscaler (HPA) to scale pods based on CPU and memory utilization.
- B
Configure the VMware Tanzu Application Service (TAS) to dynamically add nodes to the Kubernetes cluster.
- C
Leverage the Kubernetes Vertical Pod Autoscaler (VPA) to adjust container resource requests and limits automatically.
- D
Implement a custom autoscaling solution using Kubernetes Custom Resource Definitions (CRDs) and controllers.
- E
Use the Tanzu Mission Control (TMC) autoscaling feature to directly scale pods in the cluster.
Show answer and explanation
Correct answers: A, C, D
Explanation
In a VMware Tanzu-managed Kubernetes environment, application autoscaling can be achieved using Kubernetes' native tools like the Horizontal Pod Autoscaler (HPA) and Vertical Pod Autoscaler (VPA). These tools are designed to scale workloads dynamically based on resource utilization or custom metrics. Additionally, custom autoscaling solutions using Kubernetes CRDs and controllers can be implemented for advanced or unique requirements. However, tools like Tanzu Application Service (TAS) and Tanzu Mission Control (TMC) are not directly involved with application-level autoscaling in Kubernetes.
- A. Correct.
The Kubernetes Horizontal Pod Autoscaler (HPA) is a standard and recommended method to scale pods based on metrics such as CPU, memory, or custom metrics. It is commonly used in Tanzu-managed clusters.
- B. Incorrect.
The VMware Tanzu Application Service (TAS) is not directly related to Kubernetes pods or cluster-level scaling. It provides a platform-as-a-service (PaaS) environment and does not control Kubernetes cluster autoscaling.
- C. Correct.
The Kubernetes Vertical Pod Autoscaler (VPA) adjusts container resource requests and limits automatically. It complements the Horizontal Pod Autoscaler (HPA) by optimizing resource usage, making it suitable for application autoscaling in Tanzu environments.
- D. Correct.
Custom autoscaling solutions can be implemented using Kubernetes Custom Resource Definitions (CRDs) and controllers. This approach provides flexibility for specific use cases and is compatible with Tanzu-managed Kubernetes clusters.
- E. Incorrect.
Tanzu Mission Control (TMC) does not directly provide pod-level autoscaling functionality. It is primarily used for managing the lifecycle of Kubernetes clusters and enforcing policies across clusters.