NKP uses Cluster API (CAPI) to provision and manage Kubernetes clusters across supported infrastructures, including Nutanix AHV, vSphere, AWS, and GCP. CAPI components, such as controllers and providers, are deployed to manage the lifecycle of clusters on these platforms. However, when NKP attaches to a managed Kubernetes service like Azure Kubernetes Service (AKS), CAPI components are not deployed because AKS is managed by Azure, and NKP only integrates with the cluster for fleet management, not provisioning.
The NKPA course explains: “For managed Kubernetes services like AKS, NKP attaches the cluster to its management plane without deploying CAPI components, as the underlying infrastructure is managed by the cloud provider.” The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide reinforces this: “CAPI is used for NKP-managed clusters on Nutanix, vSphere, AWS, and GCP, but not for attached managed services like AKS.”
Incorrect Options:
A. vSphere: NKP deploys CAPI components (e.g., CAPV provider) to manage vSphere-based clusters.
B. GCP: NKP deploys CAPI components (e.g., CAPG provider) for GCP-based clusters.
C. Nutanix: NKP deploys CAPI components (e.g., CAPA provider for AHV) for Nutanix AHV clusters.
[:, Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Infrastructure Support., Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on CAPI Integration., Nutanix Cloud Bible, NutanixKubernetesPlatform Section:https://www.nutanixbible.com, ]
Submit