openshift-ci-robot
commented
3 weeks ago @simonpasquier: This pull request explicitly references no jira issue.
In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2482):
>kubernetes-monitoring/kubernetes-mixin is pinned to the latest upstream commit before the project switched to Grafana v11 since it broke the Kubernetes dashboards in the OCP console (see 2399dc84 for details).
>
>This change removes the Kubernetes dashboards from the jsonnet generation code. Instead their current version is copied to the `0000_90_cluster-monitoring-operator_02-dashboards.yaml` file under the `manifests/` directory. Any future update to these dashboards should be made to the manifest file directly.
>
>A follow-up PR will unpin the kubernetes-monitoring/kubernetes-mixin version.
>
>
>
>* [ ] I added CHANGELOG entry for this change.
>* [ ] No user facing changes, so no entry in CHANGELOG was needed.
>
Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
simonpasquier
rexagod
openshift-ci[bot]
openshift-bot
kubernetes-monitoring/kubernetes-mixin is pinned to the latest upstream commit before the project switched to Grafana v11 since it broke the Kubernetes dashboards in the OCP console (see 2399dc84 for details).
This change removes the Kubernetes dashboards from the jsonnet generation code. Instead their current version is copied to the
0000_90_cluster-monitoring-operator_02-dashboards.yamlfile under themanifests/directory. Any future update to these dashboards should be made to the manifest file directly.A follow-up PR will unpin the kubernetes-monitoring/kubernetes-mixin version.