-
Bug
-
Resolution: Unresolved
-
Undefined
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
As we use kubectl logs -n openshift-insights insights-runtime-extractor-xxxx, we see the default container logs is kube-rbac-proxy, like :
Defaulted container "kube-rbac-proxy" out of: kube-rbac-proxy, exporter, extractor W0915 08:00:16.108839 options.go:149] ==== Removed Flag Warning ====================== logtostderr is removed in the k8s upstream and has no effect any more. =============================================== I0915 08:00:16.109835 kube-rbac-proxy.go:530] Reading config file: /etc/kube-rbac-proxy/config-file.yaml I0915 08:00:16.109835 kube-rbac-proxy.go:233] Valid token audiences:
But most of the time we just care about the container extractor or exporter logs , not the kube-rbac-proxy
Version-Release number of selected component (if applicable):
4.19
How reproducible:
It naturally exists.
Steps to Reproduce:
1. Build an OCP cluster.
2. View the runtime-extractor pod logs.
Actual results:
The runtime extractor pod has some logs about kube-rbac-proxy
Expected results:
The runtime extractor pod only has logs for the extractor or exporter.
Additional info:
