[Conduct NKP Fleet Management] A Cloud Engineer wishes to attach existing AKS clusters to a newly deployed NKP management cluster. What should the…

To attach an existing Azure Kubernetes Service (AKS) cluster to Nutanix Kubernetes Platform (NKP) for fleet management, a new service account must be created on the AKS cluster. The default kubeconfig file generated by the Azure CLI (az aks get-credentials) uses an Azure-specific authentication provider that requires interactive login or an existing Azure session. NKP's Kommander component, which runs as a service, cannot use this mechanism. Instead, it requires a self-contained, non-interactive authentication method, which is achieved by creating a service account and using its long-lived authentication token to build a new, compatible kubeconfig file for the attachment process.

B: This is incorrect. The kubelet is a fundamental component of every Kubernetes node, including those in an AKS cluster. KIB-prep is a process for air-gapped NKP installations, not for attaching existing clusters.

C: This is incorrect. Modern AKS clusters use containerd as the container runtime. Furthermore, NKP Kommander interacts with the Kubernetes API server, not directly with the node's container runtime for management.

D: This is incorrect. Cert-manager is a core component of NKP's management plane, but it is not deployed by default on a standard AKS cluster, so there is no inherent conflict to consider.

1. Nutanix Kubernetes Platform Administration Guide: In the section on fleet management

the guide specifies the procedure for attaching existing clusters from cloud providers. It states

"For managed Kubernetes clusters from cloud providers (for example

EKS

AKS

or GKE)

you must create a service account on the cluster and then create a kubeconfig file that NKP can use to access the cluster."

Source: Nutanix Portal (Requires login) -> Documentation -> Nutanix Kubernetes Platform -> Administration Guide. The principle is detailed in the "Attaching an Existing Cluster to NKP" section.

2. D2iQ Kommander Documentation (Foundation for NKP): The process is explicitly detailed

requiring the creation of a ServiceAccount and ClusterRoleBinding on the target AKS cluster to generate a token-based kubeconfig for Kommander.

Source: D2iQ Kommander Documentation

"Attach an AKS Cluster". URL: https://docs.d2iq.com/dkp/kommander/latest/operations/attach-aks/ (Note: NKP is based on D2iQ DKP technology

making this a primary source for technical procedures).