The Nutanix Kubernetes Platform (NKP) integrates Velero, an open-source tool, for backup and restore operations as part of its Day 2 operations. The NKPA course explains that after configuring a Backup Storage Location (e.g., an AWS S3 bucket) and creating a backup, administrators can view details of the backup using the Velero CLI. The correct command to view the details of a backup named testbackup is velero backup describe testbackup. This command provides a detailed description of the backup, including its status, resources included, and storage location.
The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "To inspect a Velero backup in NKP, use the velero backup describe <backup-name> command to display detailed information about the backup, such as its creation time, expiration, and included resources." The backup name (testbackup) is specified as created by the team, and no prefix like aws-velero- is indicated in the question, making option C the correct choice.
Incorrect Options:
* A. kubectl get backupstoragelocations -n ${testbackup} -o yaml: This command retrieves Backup Storage Location objects, not backup details. The namespace ${testbackup} is also incorrect, as Velero resources are typically in a specific namespace (e.g., velero).
* B. velero backup describe aws-velero-testbackup: The backup name is testbackup, not aws-velero- testbackup. The NKPA course does not indicate any prefix for the backup name.
* D. kubectl get backupstoragelocations -n ${WORKSPACE_NAMESPACE} -o yaml: This retrieves Backup Storage Locations, not the backup itself, and does not provide backup details.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Backup and Restore with Velero.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Velero Documentation: https://velero.io

To create a FIPS-compliant NKP deployment in an air-gapped environment, the following must be done:
* Verify the OS (RHEL) itself is in FIPS mode.
* When building the image, include both the offline fips and fips overrides to ensure the image and components are built in compliance.
* When deploying the cluster, include FIPS-specific references for both Kubernetes and etcd components.
Exact extract:
"For FIPS deployments, ensure the OS is in FIPS mode, and include both offline fips and fips overrides during image creation to ensure compliant images and deployment." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Deploying NKP in FIPS Environments" NCP-CN 6.10 Study Guide - "FIPS Compliance Best Practices"
=======

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 list docker containers 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." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Bootstrap Cluster Creation Requirements" NCP-CN 6.10 Study Guide - "Bootstrap Cluster Creation Dependencies"

The NKPA course explains that NKP provides a role-based access control (RBAC) system to manage permissions within its platform, in addition to Kubernetes-native RBAC. For a development team needing limited permissions to perform specific tasks (deploying applications, scaling deployments, viewing logs and metrics) within a specific namespace, the appropriate access type in the NKP GUI is an NKP Role.
NKP Roles are predefined or custom roles within the NKP platform that map to Kubernetes RBAC permissions but are managed through the NKP UI for ease of use. They allow granular control over actions within a workspace or namespace, ensuring the team can perform their tasks (e.g., deploy, scale, get logs) without having access to other environments or cluster-wide resources. For example, an NKP Role like
"Developer" or a custom role can be configured to grant edit permissions in the team's namespace while restricting access elsewhere. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "In the NKP GUI, configure an NKP Role to grant limited permissions to a development team, allowing actions like deploying applications and viewing logs within their namespace while preventing unauthorized changes in other environments." Incorrect Options:
* B. Cluster Role: A Kubernetes Cluster Role grants permissions across all namespaces, which is too broad for the team's limited access requirement.
* C. Cluster Admin: This grants full administrative access to the entire cluster, far exceeding the team's needs and violating the principle of least privilege.
* D. Kommander Role: Kommander is a management component in NKP, but "Kommander Role" is not a specific access type in the NKP GUI for this purpose.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Access Control and RBAC.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Day 2 Operations.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

The Nutanix Kubernetes Platform (NKP) is designed to simplify the deployment and management of Kubernetes clusters on Nutanix infrastructure, including on-premises AHV-based clusters in dark site environments with no Internet connectivity. The requirements specified in the question-dark site, Nutanix- provided Rocky Linux VM image, and AHV-based cluster-point to a deployment scenario where the environment must be self-contained and rely on Nutanix-specific tools and resources to meet the air-gapped constraints.
According to the Nutanix Kubernetes Platform Administration (NKPA) course, deploying NKP in a dark site environment requires specific prerequisites to ensure all necessary components, such as container images, dependencies, and configuration files, are available without Internet access. The course emphasizes the use of an Air-Gapped Bundle and an existing local container registry as critical components for such deployments.
* Air-Gapped Bundle (Option B):
* The NKPA course explains that for dark site deployments, Nutanix provides an Air-Gapped Bundle, which is a comprehensive package containing all the software components, container images, and dependencies required to deploy and manage an NKP cluster without Internet connectivity. This bundle includes the Kubernetes binaries, NKP platform applications (e.g., Rook Ceph, monitoring tools), and other necessary artifacts.
* The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide specifically states: "For air-gapped environments, the Nutanix Air-Gapped Bundle is required to provide all dependencies, including container images and installation files, to deploy NKP clusters." This bundle is typically downloaded from the Nutanix Support Portal in an Internet-connected environment and then transferred to the dark site for deployment.
* The bundle ensures that the Nutanix-provided Rocky Linux VM image, which serves as the base operating system for the Kubernetes nodes, can be provisioned with all required software components. The NKPA course further notes that the Air-Gapped Bundle is tailored for AHV- based clusters, ensuring compatibility with the Nutanix hypervisor.
* Existing Local Container Registry (Option C):
* In a dark site environment, a local container registry is a prerequisite to store and distribute container images required by the NKP cluster. The NKPA course highlights that NKP relies on container images for Kubernetes components, platform applications, and user workloads. In an air-gapped setup, these images cannot be pulled from public registries like Docker Hub or Quay.
io.
* The course instructs administrators to set up a local container registry (e.g., Harbor, Nexus, or a Nutanix-managed registry) and populate it with the container images included in the Air-Gapped Bundle. The Nutanix Cloud Bible reinforces this, stating: "In air-gapped deployments, a local container registry must be pre-configured to host all required images, which are provided as part of the Nutanix Air-Gapped Bundle."
* The local container registry ensures that the Kubernetes nodes, running on the Nutanix-provided Rocky Linux VM image, can access the necessary images during cluster bootstrapping and operation. The NKPA course provides guidance on configuring the registry and integrating it with the NKP deployment process.
Incorrect Options:
* Konvoy Image Builder (Option A):
* Konvoy Image Builder is a tool associated with D2iQ's Konvoy platform, used to create custom machine images for Kubernetes deployments. While it can be used to build images for Kubernetes nodes, it is not a Nutanix-specific tool nor a prerequisite for NKP deployments. The NKPA course and NCP-CN 6.10 Study Guide do not mention Konvoy Image Builder, as NKP uses the Nutanix-provided Rocky Linux VM image, which is pre-configured for AHV-based clusters. This option is irrelevant to the Nutanix ecosystem.
* Self-managed AWS cluster (Option D):
* A self-managed AWS cluster is unrelated to the requirements of deploying NKP on an AHV- based cluster in a dark site. The question specifies an AHV-based cluster, which is Nutanix's Acropolis Hypervisor running on-premises, not a cloud-based AWS environment. The NKPA course focuses on Nutanix infrastructure (AHV, Prism Central) for NKP deployments and does not include AWS as a supported platform for this scenario. This option is incorrect as it contradicts the deployment environment.
Deployment Context:
* The Nutanix-provided Rocky Linux VM image is a pre-configured operating system image optimized for NKP deployments on AHV. The NKPA course notes that this image includes the necessary kernel settings, drivers, and configurations to run Kubernetes nodes efficiently on Nutanix infrastructure.
* The AHV-based cluster requirement indicates that the deployment leverages Nutanix's hypervisor, managed through Prism Central, to provision and manage the Kubernetes nodes. The Air-Gapped Bundle and local container registry ensure that all software components are available in the dark site, aligning with the NKPA course's guidelines for air-gapped deployments.
References:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Preparing the Environment for NKP Deployment.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on Air-Gapped Deployments.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com Nutanix Support Portal, Air-Gapped Bundle Documentation: https://portal.nutanix.com Nutanix Kubernetes Platform Deployment Guide: https://www.nutanix.com
=======