-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.17, 4.18, 4.19, 4.20
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Some audit events in kube-apiserver are seen repetitive and seems to be caused by kubelet. It is calling the configmap named "logging" which doesn't exist and return the response code to be 404. This is seen on most of the RHOCP versions, I have validated this on 4.16-4.20.
Version-Release number of selected component (if applicable):
RHOCP 4.20 (hosted on vSphere)
How reproducible:
100%
Steps to Reproduce:
1. Check kube-apiserver audit logs on any master node and look for the event which is calling URI ""/api/v1/namespaces/openshift-vsphere-infra/configmaps/logging?timeout=30s""
=====
"requestReceivedTimestamp": "2025-10-30T11:32:36.176961Z",
"requestURI": "/api/v1/namespaces/openshift-vsphere-infra/configmaps/logging?timeout=30s",
"responseStatus": {
"code": 404,
"details": {
"kind": "configmaps",
"name": "logging"
},
"message": "configmaps \"logging\" not found",
"metadata": {},
"reason": "NotFound",
"status": "Failure"
Actual results:
repetitive audit events streaming
Expected results:
If the configmap "logging" in "openshift-vsphere-infra" namespace doesn't exist and is not required, then no component in RHOCP should call for that configmap.
Additional info: