The collectors (Vector) restart impacts in the KubeAPI in RHOCP 4
Issue
- After being restarted the collectors (Vector) pods, the
KubeAPIgot unresponsive - The OpenShift cluster got unresponsive observing a high number of
KubeAPIrequests coming from theserviceAccountused by the collectors pods - Observed in the control-plane nodes a high cpu and memory usage suddenly. Reviewing the KubeAPI metrics, it was observed a peak or requests to the KubeAPI coming from the serviceAccount used by the Red Hat OpenShift Logging collector pods.
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Red Hat OpenShift Logging (RHOL)
- 5.8
- 5.9
- 6.0
- 6.1
- 6.2
- 6.3
- 6.4
- Vector
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
