The primary benefit of a private registry is to ensure security and privacy for container images, especially when dealing with sensitive data and compliance requirements (such as financial or government use cases).
While secure connections to public registries like DockerHub or GitHub container registries are possible, using a private registry ensures full control over image access and auditing.
Key reference:
"Private registries ensure images remain within the security and compliance boundaries of the enterprise, avoiding potential risks associated with public SaaS registries." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Private Registry Use Cases and Benefits" NCP-CN 6.10 Study Guide - "Security and Compliance Considerations"

The NKPA course specifies the supported operating systems for NKP clusters deployed using the Nutanix provisioning method (CAPX), which leverages Cluster API for Nutanix (CAPX) to provision clusters on Nutanix AHV. The supported OS platforms for CAPX are Rocky Linux and Ubuntu, as these distributions are tested and optimized for Nutanix infrastructure and Kubernetes requirements.
Rocky Linux is a CentOS replacement adopted by Nutanix after CentOS 8's end-of-life in 2021, providing a stable, enterprise-grade OS. Ubuntu, particularly LTS versions like 20.04 or 22.04, is widely supported due to its compatibility with Kubernetes and Nutanix AHV. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "When deploying NKP with the Nutanix provisioning method (CAPX), the supported OS platforms are Rocky Linux and Ubuntu, ensuring compatibility with Nutanix AHV and Kubernetes." These OS images are typically prepared using NKP Image Builder (NIB) to include necessary components like kubeadm and containerd.
Incorrect Options:
* A. CentOS and Rocky Linux: CentOS 8 is no longer supported post-2021, and Nutanix has shifted to Rocky Linux.
* C. Flatcar, Rocky Linux, and Ubuntu: Flatcar Container Linux is not a supported OS for CAPX in NKP deployments.
* D. CentOS and Ubuntu: CentOS is not supported, as noted above.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Nutanix Provisioning with CAPX.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on NKP Deployment Prerequisites.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

As per the NKPA 6.10 documentation, the standard and supported approach for installing Kommander on an NKP cluster is using the NKP CLI. The CLI provides commands for deploying Kommander and associated platform components as part of the cluster lifecycle management workflow.
Key Reference:
"The recommended approach to deploy Kommander is by using the nkp CLI, which ensures compatibility and streamlined installation with the rest of the Nutanix Kubernetes Platform stack." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Installing Kommander with NKP CLI" NCP-CN 6.10 Study Guide - "Kommander Installation and Management"

As per the NKPA 6.10 documentation, the primary requirement for attaching external (self-managed) Kubernetes clusters to NKP is network connectivity. Specifically, the NKP management cluster must be able to communicate with the Kubernetes API server and relevant services of the target cluster. This allows NKP to collect metrics, perform health checks, and manage the attached cluster through Kommander and associated tools.
Exact extract:
"For attaching existing Kubernetes clusters, ensure the NKP management cluster can reach the Kubernetes API server of the target cluster and that the kubeconfig used has sufficient permissions." There is no requirement that the Kubernetes versions be exactly matched or within N-1, nor that an NKP admin account be directly established on the target clusters; the connectivity and valid kubeconfig file are the essential requirements.
Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Attaching External Clusters" NCP-CN 6.10 Study Guide - "External Cluster Integration"

As per the NKPA 6.10 documentation, the correct approach for deleting an entire NKP-managed cluster (including nodes and deployed applications) is to use the nkp delete cluster command with the cluster name and --kubeconfig parameter. The --self-managed flag ensures the deletion of resources provisioned by the cluster.
Exact extract:
"Use nkp delete cluster --cluster-name=<name> --self-managed --kubeconfig=<config> to delete a cluster and its associated resources." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Cluster Deletion Workflow" NCP-CN 6.10 Study Guide - "Deleting a Managed Cluster"
=======