Ressource leaking detection

Resource "Leaking" Detection

Sometimes, high-frequency automated tasks create thousands of events or secrets, which can slow down the cluster database.

Resolution Steps

• Count Objects: Check if a single namespace has an unusually high number of objects (e.g., >1000 secrets or configmaps).

oc get all -n <namespace> | wc -l
Identify Event Flooding: Look for a specific resource that is generating thousands of warnings.

oc get events -A --sort-by='.count'

Escalation Criteria: > 1. If an ETCD member is Unhealthy or the operator is Degraded, escalate to L2 Cluster Admins immediately. ETCD issues can lead to total cluster failure. 2. If a namespace is stuck in Terminating and clearing resources doesn't work, do not attempt to "force delete" via the API; escalate to L2.