My Setup: - kubernetes (3 master, 10 worker) rocky linux 9.6 - Splunk OTel Collector deployed via Helm chart - Agents are exporting to Splunk Olly (metrics are coming in)   My Problem: Metrics like k8s.pod.cpu.utilization, k8s.node.memory.usage... etc are not arriving. Other metrics (host metrics, k8s.pod.network.io) are showing up Thats why inside the kubernetes infrastructure the "by CPU request" charts show "no data", while the networks charts are working.   What I have tried / fixed: - TLS error fixed with insecure_skip_verify: true - Forbidden issue fixed with rbac.customRules Confirmed: - kubeletstats scrapes with no errors - collector internal telemetry confirms data is shipped - metrics pipeline has kubestats -> processors -> signalfx   I suspect that  pod/node metrics are disabled by default. Which container/pod CPU & memory metrics are disabled by default? I tried doing everything from this page: Missing metrics | Observability Cloud (last updated 2025-07-16T18:48:35.249Z)   My values.yaml: also attached below clusterName: "my-pod-cluster" splunkObservability: realm: "eu1" accessToken: "**************" metricsEnabled: true tracesEnabled: true profilingEnabled: true infrastructureMonitoringEventsEnabled: true splunkPlatform: endpoint: "************************************************************************************" token: "****************************" index: "cw-ccitm-lab-k8s_e" logsEnabled: true insecureSkipVerify: false logsCollection: containers: enabled: true environment: lab gateway: enabled: false agent: config: processors: resource/node: attributes: - action: upsert key: host.name value: "${K8S_NODE_NAME}" service: pipelines: metrics: receivers: - host_metrics - kubeletstats - otlp processors: - memory_limiter - batch - resourcedetection - resource/node - k8sattributes receivers: kubelet_stats: insecure_skip_verify: true metric_groups: - node - pod - container - volume metrics: k8s.node.cpu.time: enabled: true k8s.pod.cpu.time: enabled: true resources: requests: cpu: 100m memory: 128Mi extraEnvs: - name: HTTP_PROXY value: "http://10.89.3.2:80" - name: HTTPS_PROXY value: "http://10.89.3.2:80" - name: NO_PROXY value: "localhost,127.0.0.1,10.0.0.0/8" - name: K8S_NODE_NAME valueFrom: fieldRef: fieldPath: spec.nodeName clusterReceiver: extraEnvs: - name: HTTP_PROXY value: "http://10.89.3.2:80" - name: HTTPS_PROXY value: "http://10.89.3.2:80" - name: NO_PROXY value: "localhost,127.0.0.1,10.0.0.0/8"     ... View more