A Platform Engineer has been tasked with building a custom image for the deployment of...

The Nutanix Kubernetes Platform (NKP) uses the Kubernetes Image Builder (KIB) or Nutanix Image Builder (NIB) to create custom machine images for NKP management and worker nodes. These images are tailored to include specific versions of Kubernetes, container runtimes (e.g., containerd), and other dependencies. The NKPA course specifies that KIB relies on Ansible playbooks to configure the image, and the versions of packages like Kubernetes and containerd are defined in Ansible configuration files.

The correct location to verify the package versions isansible/group_vars/all/defaults.yaml. This file contains the default variables used by Ansible during the image-building process, including the versions of Kubernetes and containerd. For example, it may include entries like kubernetes_version: 1.30.5 and containerd_version: 1.7.22. The Nutanix Cloud Native (NCP-CN) 6.10 Study Guide states: “To ensure the correct versions of Kubernetes and containerd are used in KIB, check the ansible/group_vars/all/defaults.yaml file, which specifies the package versions for the image build.” The engineer can review and modify this file to confirm that the security team’s authorized versions (Kubernetes 1.30.5 and containerd 1.7.22) are being used.

Incorrect Options:

A. config/pulumi/vars/pulumi.kib.config: Pulumi is an infrastructure-as-code tool, but it is not used by KIB for specifying package versions. The NKPA course does not reference this file.

B. terraform/vars/default/terraform.tfvars: Terraform is used for infrastructure provisioning, not for defining software versions in KIB images.

D. The custom image's .env file: KIB does not use a .env file for version configuration; Ansible variables are used instead.