The NKPA course specifies that air-gapped deployments and centralized fleet management of multiple clusters are advanced features of NKP, requiring the NKP Ultimate license tier. The Ultimate tier includes support for air-gapped environments (via Air-Gapped Bundles) and fleet management capabilities, such as attaching and managing multiple clusters under a single management plane, which is critical for the national defense company's scenario.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "The NKP Ultimate license tier is required for air-gapped deployments and centralized management of multiple Kubernetes clusters, providing the necessary tools for secure, isolated environments." This ensures the company can deploy and manage their three clusters in an air-gapped setup while maintaining strict data security.
Incorrect Options:
* A. NKP Starter: The Starter tier lacks air-gapped and fleet management features.
* C. NKP Pro: The Pro tier may support some advanced features but not air-gapped deployments or full fleet management.
* D. NKP UI: This is not a license tier; it's a UI component of NKP.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Licensing and Fleet Management.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Air-Gapped Deployments.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

The NKPA course details the process for upgrading an NKP-managed Kubernetes cluster, such as one running on AWS from version 1.28.1 to 1.29.9. Upgrading a Kubernetes cluster involves two distinct steps:
upgrading the control plane nodes and upgrading the worker nodes, ensuring minimal disruption and maintaining compatibility. The NKP CLI provides specific commands to handle these upgrades separately for AWS clusters.
* Upgrade Control Planes with nkp update controlplane aws --cluster-name=${CLUSTER_NAME}
--ami AMI_ID --kubernetes-version=v1.29.9 (Option B):The control plane must be upgraded first to the target Kubernetes version (1.29.9). The nkp update controlplane aws command updates the control plane nodes, specifying the cluster name, the new Kubernetes version, and an updated AMI (Amazon Machine Image) that supports the target version. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "To upgrade an NKP cluster on AWS, first update the control plane using nkp update controlplane aws --cluster-name <name> --ami <ami-id> --kubernetes-version <version> to ensure the control plane runs the desired Kubernetes version." The --ami flag is required to specify a compatible image for the upgraded control plane nodes.
* Upgrade Workers with nkp upgrade nodepool aws ${NODEPOOL_NAME} --cluster- name=${CLUSTER_NAME} --kubernetes-version=v1.29.9 (Option C):After the control plane is upgraded, the worker nodes in each node pool must be upgraded to match the control plane version.
The nkp upgrade nodepool aws command updates the specified node pool to the target Kubernetes version (1.29.9). The NKPA course notes: "Upgrade worker nodes using nkp upgrade nodepool aws
<nodepool-name> --cluster-name <cluster-name> --kubernetes-version <version>, which performs a rolling update to ensure minimal downtime." This command automatically handles the rolling update of worker nodes, replacing them with new nodes running the updated version. Note that the --ami flag is not required here, as NKP typically uses the same AMI as the control plane or retrieves a compatible one based on the version.
Incorrect Options:
* A. nkp update nodepool aws: The correct command is nkp upgrade nodepool, not nkp update nodepool. The NKPA course uses upgrade for version changes to node pools.
* D. nkp update cluster aws: This command is not the standard approach for upgrading Kubernetes versions in NKP. The course specifies separate commands for control plane and node pool upgrades to ensure a controlled process.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Cluster Upgrades.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

The error states:
pgsql
Copy
error upgrading CAPI components: unable to upgrade CAPI components: deployment "capp-controller- manager" is not ready after 10m0s: failed to connect to the management cluster: context deadline exceeded This clearly points to connectivity issues between the VM (or nodes) and the management cluster, typically caused by registry communication issues in air-gapped or private environments. When the VM cannot connect to the registry to pull required images or configuration, the CAPI (Cluster API) components cannot be initialized, causing a timeout.
Key Reference:
* Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Air-Gapped and Registry Communication Issues"
* NCP-CN 6.10 Study Guide - "Cluster API Upgrade Process and Network Prerequisites"
=======

When an attached cluster (e.g., an external cluster like EKS) is stuck in a 'deleting' state in the NKP UI, it indicates an issue with the reconciliation process in the NKP management cluster. The NKPA course explains that attached clusters are represented in NKP as KommanderCluster custom resources in the management cluster. To resolve a stuck deletion, the engineer must manually delete the KommanderCluster resource using kubectl in the context of the NKP management cluster.
The correct command is kubectl delete kommandercluster, executed in the context of the NKP management cluster (not the attached cluster). For example: kubectl delete kommandercluster <cluster-name> -n
<namespace>. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "If an attached cluster is stuck in a 'deleting' state, delete the corresponding KommanderCluster resource in the NKP management cluster using kubectl delete kommandercluster to remove it from management." This ensures the cluster is fully detached and removed from the UI.
Incorrect Options:
* A. kubectl delete cluster: There is no cluster resource type in this context; the correct resource is kommandercluster.
* B. nkp delete kommandercluster: The nkp CLI does not have a delete kommandercluster subcommand.
* D. nkp delete cluster in the attached cluster: This command is for deleting NKP-managed clusters, not detaching external clusters, and it should be run from the management cluster context.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Fleet Management.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Detaching Clusters.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

For deploying NKP clusters in AWS, setting the AWS_REGION environment variable is a key prerequisite to ensure that the AWS CLI and underlying deployment scripts know which region to target. This is essential for provisioning instances using the specified AMI.
Exact extract:
"Set the AWS_REGION environment variable to the appropriate region prior to deploying clusters to ensure proper interaction with the AWS API." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "AWS Environment Configuration" NCP-CN 6.10 Study Guide - "Preparing the AWS Environment for NKP"