2V0-71.23 Question 201
Select 3You are a Kubernetes administrator managing a Tanzu Kubernetes Grid (TKG) deployment. Your organization requires the ability to scale clusters dynamically, upgrade Kubernetes versions seamlessly, and ensure consistency across environments. Which features or capabilities of TKG cluster lifecycle management can help you achieve these goals?
- A
Cluster API (CAPI) integration for declarative cluster management
- B
Manual configuration of kubelet parameters on each node
- C
Rolling upgrades for Kubernetes clusters in TKG
- D
Support for scaling clusters horizontally by adding or removing worker nodes
- E
Direct modification of control plane VMs via SSH for custom changes
Show answer and explanation
Correct answers: A, C, D
Explanation
Tanzu Kubernetes Grid (TKG) leverages Cluster API (CAPI) to provide declarative and automated cluster lifecycle management. This includes creating, scaling, and upgrading clusters. Features like rolling upgrades and horizontal scaling align with TKG's design principles to ensure seamless operations. However, manual or direct modifications to individual nodes or control plane VMs are not part of the recommended practices in TKG, as they can disrupt the consistency and manageability of clusters.
- A. Correct.
Cluster API (CAPI) integration is a core component of TKG, enabling declarative cluster lifecycle management, including creation, scaling, and upgrades.
- B. Incorrect.
Manually configuring kubelet parameters on each node goes against the declarative and automated approach that TKG promotes. Such actions are not recommended in TKG cluster lifecycle management.
- C. Correct.
Rolling upgrades are a supported feature in TKG, allowing Kubernetes clusters to be upgraded with minimal downtime and without disrupting workloads.
- D. Correct.
TKG supports horizontal scaling of clusters by adding or removing worker nodes dynamically, aligning with the goal of managing cluster lifecycle efficiently.
- E. Incorrect.
Direct modification of control plane VMs via SSH is not recommended or supported in TKG, as it can lead to inconsistencies and is outside the scope of managed cluster lifecycle operations.