TMC SM cluster-secret and cluster-config pods CrashLoopBackOff with OOMKilled

Products

• VMware Tanzu Platform - Kubernetes

Issue/Introduction

The cluster-secret and cluster-config pods on an attached guest cluster experience a CrashLoopBackOff (CLBO) state with an OOMKilled status.

Cause

The memory resource limit is set to 256Mi for the cluster-secret and cluster-config deployments, which is insufficient for clusters containing a large volume of resources. This memory exhaustion causes the pods to be OOMKilled while attempting to watch these resources.

The resource settings are not natively configurable for the TMC agents.

Resolution

A permanent fix for this issue will be included in an upcoming release of TMC SM.

If a temporary workaround is required to adjust the agent resource limits prior to the fix release, engage Broadcom Technical Support for assistance.