[Perform Day 2 Operations] A dev team needed to optimize their logging system to be more robust, because the CPU and memory limits were insufficient…

To customize a platform add-on like the logging operator in Nutanix Kubernetes Platform (NKP), you must create a ConfigMap with a specific name (-overrides) in the kommander namespace. The question requires increasing Fluentd's CPU and memory limits. Option B presents a syntactically correct YAML definition for a ConfigMap named logging-operator-logging-overrides. The data key values.yaml contains a properly structured YAML block that sets the fluentd.resources.limits and fluentd.resources.requests to the desired values of 4 CPU and 4Gi memory, which directly addresses the performance issue described.

A: The YAML syntax is invalid (e.g., apiVersion v1, metadataname), and the embedded values under data are malformed and do not follow the required hierarchical structure.

C: This option contains invalid YAML syntax and a malformed, duplicated values.yaml block, making it non-functional. The resource values are also incorrectly assigned.

D: While the outer ConfigMap structure is mostly correct, the embedded values.yaml data is not valid YAML. It is a single line of text without the necessary indentation and structure.

1. Nutanix Kubernetes Platform Administration Guide - Customizing a Platform Add-on: This official guide details the procedure for customizing platform add-ons. It specifies creating a ConfigMap named -overrides in the kommander namespace and providing custom settings in the data.values.yaml key. The structure used in option B aligns with this documented method.

URL: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Kubernetes-Platform-Admin-Guide-v28:ecm-customize-addon-t.html

2. Kubernetes Documentation - Resource Management for Pods and Containers: This official Kubernetes documentation explains the syntax for specifying resource requests and limits within a Pod specification. The resources.limits.cpu

resources.limits.memory

etc.

structure shown in Option B is the standard Kubernetes convention.

URL: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ (Section: "Resource requests and limits of a container")