-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.18.0
-
None
-
Low
-
None
-
MON Sprint 260
-
1
-
False
-
Description of problem:
"setting componentGlobalsRegistry in SetFallback" in metrics-server logs, only for 4.18, no issue with 4.17
$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.18.0-0.nightly-2024-09-12-023938 True False 4h4m Cluster version is 4.18.0-0.nightly-2024-09-12-023938 $ oc -n openshift-monitoring logs metrics-server-5db86884bd-pr7kj W0912 05:48:18.427536 1 registry.go:345] setting componentGlobalsRegistry in SetFallback. We recommend calling componentGlobalsRegistry.Set() right after parsing flags to avoid using feature gates before their final values are set by the flags. I0912 05:48:18.735931 1 handler.go:286] Adding GroupVersion metrics.k8s.io v1beta1 to ResourceManager I0912 05:48:18.841826 1 dynamic_cafile_content.go:160] "Starting controller" name="request-header::/etc/client-ca-bundle/requestheader-client-ca-file" ...
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2024-09-12-023938 with metrics-server 0.7.2
How reproducible:
always
Steps to Reproduce:
1. check metrics-server pog logs
Actual results:
warning message "setting componentGlobalsRegistry in SetFallback" in metrics-server logs
Expected results:
Additional info:
no functional impact
