A VKS administrator is tasked to leverage day-2 controls to monitor, scale, and optimize Kubernetes...

VCF 9.0 describes a vSphere Namespace as the control point where administrators defineresource boundariesfor workloads, explicitly stating that vSphere administrators can create namespaces and “configure them with specified amount ofmemory, CPU, and storage,” and that you can “set limits forCPU, memory, storage” for a namespace. This directly supports stepAas a day-2 control to keep multi-tenant clusters governed and prevent resource contention across different teams and workload types.

For monitoring and optimization, VCF 9.0 explains that day-2 operations include visibility into utilization and operational metrics for VKS clusters, noting that application teams can use day-2 actions and gain insights intoCPU and memory utilizationand advanced metrics (including contention and availability) for VKS clusters. In addition, VCF 9.0 monitoring guidance for VKS clusters states thatTelegraf and Prometheusmust be installed and configured on each VKS cluster before metrics and object details are sent for monitoring, and that VCF Operations supports metrics collection for Kubernetes objects (namespaces, nodes, pods, containers) via Prometheus. Since the Prometheus stack commonly includes Grafana dashboards for visualization, deployingPrometheus + Grafanamatches the required monitoring/optimization outcome inC.