As per the NKPA 6.10 documentation and cluster autoscaler behavior, when nodes are scaled down in NKP (or any CAPI-managed environment), the node is deleted from the infrastructure provider (vSphere, AWS, Nutanix, etc.). This effectively removes it from both the cluster and the underlying hypervisor or cloud provider, thus freeing up resources and reducing costs.
Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Cluster Autoscaler Node Deletion Behavior" NCP-CN 6.10 Study Guide - "Autoscaler Impact on Infrastructure Resources"

According to the NKPA 6.10 documentation, the Pre-provisioned infrastructure provider (CAPPP) requires the user to provide an inventory file of the servers that will become the cluster nodes. This inventory file contains connection information (IP addresses, credentials, etc.) for each pre-provisioned node, enabling the Cluster API to connect and configure these servers directly during cluster creation.
Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "CAPPP (Pre-Provisioned) Overview" NCP-CN 6.10 Study Guide - "Inventory Files for Pre-Provisioned Infrastructure"
=======

A bastion host in a dark site environment serves as a secure entry point for managing the NKP deployment, providing access to the cluster infrastructure without direct Internet connectivity. The NKPA course outlines the prerequisites for preparing a Linux VM as a bastion host, focusing on secure access and time synchronization, which are critical for air-gapped Kubernetes deployments.
* Get or create SSH Keys (Option B):The bastion host requires SSH keys to enable secure, passwordless access to the NKP cluster nodes and other infrastructure components (e.g., Nutanix AHV hosts). The NKPA course specifies that SSH keys must be generated or obtained and configured on the bastion host to facilitate secure communication during deployment and management tasks. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: "For a bastion host in an NKP dark site deployment, ensure SSH keys are created or obtained to enable secure access to cluster nodes and infrastructure." The engineer can generate SSH keys using ssh-keygen and distribute the public key to the target systems.
* Enable NTP Service (Option D):Time synchronization is essential in Kubernetes clusters to ensure consistent logging, certificate management, and scheduling. In a dark site with no Internet access, the bastion host must be configured to synchronize time with an internal NTP (Network Time Protocol) server or act as an NTP server itself. The NKPA course emphasizes enabling the NTP service on the bastion host to maintain accurate time across the air-gapped environment. The NCP-CN 6.10 Study Guide notes: "Enable the NTP service on the bastion host to ensure time synchronization in a dark site NKP deployment, as Kubernetes requires accurate time for proper operation." The engineer can enable NTP using commands like systemctl enable ntpd and configure it to use an internal time source.
Incorrect Options:
* A. Install LDAP Server: LDAP is used for centralized authentication, but it is not a requirement for a bastion host in an NKP dark site deployment. The course focuses on SSH access instead.
* C. Install Docker: While Docker is needed on Kubernetes nodes for container runtimes, the bastion host's role is to provide secure access and management, not to run containers.
:
Nutanix Kubernetes Platform Administration (NKPA) Course, Section on Preparing for Dark Site Deployments.
Nutanix Cloud Native (NCP-CN) 6.10 Study Guide, Chapter on NKP Deployment Prerequisites.
Nutanix Cloud Bible, NutanixKubernetesPlatform Section: https://www.nutanixbible.com

According to the NKPA 6.10 documentation under the "Preparing for FIPS Compliance" section, the first step for enabling FIPS in an NKP environment is to ensure that the underlying operating system (OS) or OS images are correctly configured for FIPS mode. The Nutanix Kubernetes Platform can only leverage FIPS- compliant cryptographic modules if the underlying OS is already configured for FIPS operation.
Specifically, the documentation states:
"Before enabling FIPS in NKP, ensure that the OS or OS images are prepared and configured to operate in FIPS mode, following the vendor's guidelines. Once the OS is in FIPS mode, the NKP cluster components can be provisioned with FIPS support." This foundational step is critical to ensure cryptographic consistency and compliance throughout the NKP stack.
Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "FIPS Compliance" NCP-CN 6.10 Study Guide - "Preparing OS Images for FIPS"
=======

According to the NKPA 6.10 documentation, Rook Ceph is the recommended out-of-the-box storage solution integrated with NKP for persistent data storage, backups, and object storage within the Kubernetes environment.
Key Reference:
"Rook Ceph is integrated with NKP for providing persistent storage and backup support within the cluster." Reference:
Nutanix Kubernetes Platform Administration (NKPA) 6.10 - "Storage Architecture in NKP" NCP-CN 6.10 Study Guide - "Rook Ceph for OOB Storage"