To deploy a Nutanix Kubernetes Platform (NKP) cluster with a minimal resource footprint, the administrator must perform a customized installation. This process involves two main steps using the nkp install kommander command set. First, the --init parameter is used to generate a default installation.yaml configuration file. Second, after editing this file to specify a minimal resource profile (e.g., essential), the --yaml parameter is used to direct the installer to use this customized file for the deployment. Both parameters are essential for the workflow of deploying a non-default, minimal resource configuration.

A. --request-timeout: This parameter configures the timeout for individual API server requests, which does not influence the allocation of system resources for the cluster components.

B. --wait-timeout: This parameter adjusts the overall time the installer waits for components to become ready. While useful in slow environments, it does not define or select a minimal resource profile.

Nutanix Kubernetes Platform 2.4 Documentation - Installing Kommander: The official documentation outlines the installation process. It specifies using nkp install kommander --init to generate the configuration file and nkp install kommander --yaml installation.yaml to apply the customized configuration. This two-step process is the standard method for non-default installations

such as selecting a specific resource profile. (Source: Nutanix Portal - Search for "Installing Kommander on the Management Cluster" in the NKP documentation).

D2iQ Kommander Documentation - Customizing the Installation: NKP is based on D2iQ Kommander. The D2iQ documentation details the use of --init to create the installation.yaml and --yaml to apply it. It also describes setting resourceProfile: essential within the YAML for minimal deployments. (Source: D2iQ Kommander Documentation

Installation section).