Description of problem: login 4.11.0-0.nightly-2022-05-20-213928 hypershift cluster with Guest cluster kubeconfig, still see setting for grafana in cluster-monitoring-config configmap. from 4.11, grafana is removed, should not set it. see all 4.11 monitoring components from: https://github.com/openshift/cluster-monitoring-operator/blob/release-4.11/pkg/manifests/config.go#L109-L121 # oc -n openshift-monitoring get cm cluster-monitoring-config -oyaml apiVersion: v1 data: config.yaml: | alertmanagerMain: null enableUserWorkload: null grafana: null http: null k8sPrometheusAdapter: null kubeStateMetrics: null openshiftStateMetrics: null prometheusK8s: null prometheusOperator: logLevel: "" nodeSelector: kubernetes.io/os: linux tolerations: null telemeterClient: null thanosQuerier: null kind: ConfigMap metadata: creationTimestamp: "2022-05-23T03:29:46Z" labels: hypershift.io/managed: "true" name: cluster-monitoring-config namespace: openshift-monitoring resourceVersion: "1516" uid: 02a7ae1e-4f03-4b85-bda5-871fa187cd10 Version-Release number of selected component (if applicable): 4.11.0-0.nightly-2022-05-20-213928 How reproducible: always Steps to Reproduce: 1. check cluster-monitoring-config configmap content in a hypershift default cluster 2. 3. Actual results: still see setting for grafana. Expected results: should not see grafana setting Additional info:
I think this is a bug for HyperShift folks as this is not a problem of CMO but of the HyperShift controller which has an outdated version of the CMO ConfigMap this should be updated https://github.com/openshift/hypershift/tree/main/thirdparty
see from https://bugzilla.redhat.com/show_bug.cgi?id=2089224#c10 default configmap cluster-monitoring-config is removed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069