When deploying NKP to AWS, the bootstrap process requires AWS credentials to interact with AWS APIs for provisioning resources like EC2 instances. The NKPA course specifies that the nkp CLI supports the --aws-profile flag to specify a custom AWS profile for authentication. This profile, defined in the AWS credentials file (~/.aws/credentials), contains the access key and secret key for the desired AWS account.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To deploy NKP on AWS with custom credentials, use the --aws-profile= flag during the nkp create bootstrap command to reference a specific AWS profile.” This approach leverages the AWS CLI’s profile management, ensuring secure and flexible credential handling. For example, the command would be nkp create bootstrap --aws-profile=my-profile --kubeconfig bootstrap-cluster.conf.

Incorrect Options:

B. --cloud-credentials=<my-profile></my-profile>: This flag is not used by the nkp CLI. The NKPA course specifies --aws-profile for AWS.

C. --with-aws-bootstrap-credentials=true: This flag does not exist in the NKPA documentation for NKP bootstrap.

D. --aws-access-key=<aws access="" key=""> --aws-secret-key=<aws secret="" key=""></aws></aws>: While these flags may be used in some tools, the NKPA course recommends using --aws-profile to avoid hardcoding sensitive credentials.

According to theNKPA 6.10 documentation, licensing in an NKP cluster is constrained by the total number of vCPUs assigned to all nodes (workers and control planes). In this scenario, the cluster has a maximum of 150 vCPUs available.

The existing output shows 10 worker nodes, each with 8 vCPUs (10×8=80 vCPUs) and 3 control plane nodes, each with 4 vCPUs (3×4=12 vCPUs).

Current vCPU usage: 80 + 12 = 92 vCPUs.

Remaining vCPUs: 150 - 92 = 58 vCPUs.

Option A:

Adding 6 control plane nodes (6×4=24 vCPUs).

This would increase control planes to 9 total (3 existing + 6 new). Control plane nodes would consume 9×4=36 vCPUs.

Worker nodes remain at 80 vCPUs.

Total vCPU usage: 36 + 80 = 116 vCPUs (still under 150 vCPUs).

However, it’s unusual and unnecessary to have 9 control planes in a typical NKP setup. NKPA and NCP-CN best practices indicate typically no more than 3 or 5 control planes for HA. Therefore, this is technically possible but not recommended or standard practice. So not selected.

Option B:

Expanding the existing worker nodepool by 8 nodes (8×8=64 vCPUs).

This would add 64 vCPUs to the current 92 vCPUs:

92 + 64 = 156 vCPUs → exceeds licensing limit.

Correction:The question specifies “expand up to 8 nodes,” so it’s possible to expand by only 7 nodes (7×8=56 vCPUs).

92 + 56 = 148 vCPUs → within licensing limits.

Thus, expanding byup to 7 nodesis valid.

Option C:

Creating a new worker nodepool with 10 nodes (10×8=80 vCPUs).

This would add 80 vCPUs to the existing 92 vCPUs:

92 + 80 = 172 vCPUs → exceeds 150 vCPU licensing limit.

Not valid.

Option D:

Expanding the original worker nodepool by up to 4 nodes (4×8=32 vCPUs) = +32 vCPUs.

Adding a new nodepool of 6 nodes with 4 vCPUs/node (6×4=24 vCPUs) = +24 vCPUs.

Total increase: 32 + 24 = 56 vCPUs.

Total vCPU usage: 92 + 56 = 148 vCPUs → within the 150 vCPU limit.

Thus, valid.

Extract Reference:

NKPA 6.10– “Cluster Sizing and Licensing”

Nutanix Kubernetes Platform Administration (NKPA) – Licensing Considerations

"The total number of vCPUs for all nodes (control planes and workers) must not exceed the licensed vCPU capacity of the NKP deployment."

This confirms thatOptions B and Dare the two valid approaches to expand the cluster while remaining compliant with licensing constraints.

The error message:

python

Copy

failed to list clusters: command "docker ps -a --filter label=io.x-k8s.kind.cluster --format '{{.Label "io.x-k8s.kind.cluster"}}'" failed with error: exit status 1

indicates that the command failed while attempting to listdockercontainers with the given filter. The kind tool (used for creating a bootstrap cluster) depends on Docker as the container runtime.

Root cause:

If Docker is not running or a compatible container runtime is not available (such as containerd), the kind tool cannot list or interact with the required containers, resulting in this error.

Key Reference:

“When creating bootstrap clusters, the kind tool requires Docker to be installed and running. If Docker is not running, errors will be encountered listing or interacting with containers.”

According to theNKPA 6.10 documentationand Nutanix licensing details, NKP Starter is bundled with theNCI Starterentitlement. This basic licensing tier includes essential capabilities for deploying and managing Kubernetes clusters within a Nutanix environment.

Key reference:

“NKP Starter is included with NCI Starter, providing foundational Kubernetes cluster lifecycle management features for small-scale or starter deployments.”

As per theNKPA 6.10 documentationunder “Day 2 Operations: Managing Applications”, the recommended procedure to enable an application (like NKP Insights) involves accessing the cluster’sApplication Dashboard. The NKP Insights application does not appear in the general category list if the cluster does not have the correct context or if the application category is not globally enabled.

The specific procedure to enable NKP Insights includes:

Navigate to theClusterssection from the left-side menu.

SelectView Detailsfor the target cluster (prod-01 in this case).

In theApplication Dashboardof that specific cluster, locate the NKP Insights application.

Click the three-dot menu (ellipsis) for NKP Insights and selectEnable.

The exhibit indicates an error during the creation of a bootstrap cluster using the nkp create bootstrap command in an air-gapped environment. The NKPA course explains that a bootstrap cluster is a temporary Kubernetes cluster used to initialize Cluster API (CAPI) components for provisioning the target NKP cluster. In an air-gapped environment, all required resources, including container images, must be available locally since there is no Internet access to pull them from public registries.

The most likely reason for the error is thatthe bootstrap cluster image needs to be loaded prior to creating the bootstrap cluster(Option B). The course specifies that in air-gapped deployments, the bootstrap cluster image (typically a kind or k3s image used by CAPI) must be pre-loaded into a local container registry or the bastion host before running nkp create bootstrap. This image is part of the Air-Gapped Bundle provided by Nutanix, which includes all necessary container images for NKP deployment. Without pre-loading this image, the nkp create bootstrap command fails because it cannot pull the required image.

The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “In an air-gapped NKP deployment, ensure the bootstrap cluster image (e.g., kindest/node) is loaded into a local registry or host before executing nkp create bootstrap, as the command requires this image to create the temporary cluster.” The engineer must extract the bootstrap image from the Air-Gapped Bundle, load it using docker load or similar, and configure the local registry to make it accessible during the bootstrap process.

Incorrect Options:

A. The CAPI provisioning method needs to be specified as nkp create bootstrap nutanix: The nkp create bootstrap command does not require a provisioning method like nutanix at this stage; the provider (e.g., CAPX for Nutanix) is specified during the actual cluster creation (nkp create cluster), not bootstrap creation.

C. The Ubuntu 22.04 OS image needs to be NIB-prepped prior to creating the bootstrap: The Ubuntu 22.04 image is for the target NKP cluster nodes, not the bootstrap cluster, which uses a pre-built image (e.g., kind). NIB-prepping this image is a later step.

D. The nkp create bootstrap command needs to be executed as root: While some commands may require elevated privileges, the NKPA course does not specify that nkp create bootstrap must be run as root. The error is more likely related to missing images in an air-gapped setup.

The NKPA course clarifies that NKP licenses are based on the number ofCPU coresin the infrastructure hosting the Kubernetes clusters. This licensing model applies to both on-premises (e.g., Nutanix AHV) and cloud-based deployments. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “NKP licenses are obtained based on the total number of CPU cores allocated to the clusters managed by the platform.” This core-based licensing ensures flexibility across different infrastructure types while aligning with the resource consumption of Kubernetes workloads.

Incorrect Options:

A. Flash: Flash storage is not a licensing unit for NKP.

B. CPU Sockets: Nutanix licenses for other products may use sockets, but NKP uses cores.

C. TiBs: Terabytes are used for storage licensing, not NKP.