Bug 2089574
Summary: | UWM prometheus-operator pod can't start up due to no master node in hypershift cluster | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
Component: | Monitoring | Assignee: | Joao Marcal <jmarcal> |
Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.11 | CC: | aaleman, amuller, anpicker, cewong, dmohr, jmarcal, sjenning, spasquie |
Target Milestone: | --- | ||
Target Release: | 4.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-08-10 11:13:36 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Junqi Zhao
2022-05-24 03:54:38 UTC
User workload monitoring is supported, but a requirement for HyperShift clusters is that you specify the nodeSelector for each component of user workload monitoring in the user workload monitoring configMap. The node selector can be something like: kubernetes.io/os: linux See: https://github.com/openshift/cluster-monitoring-operator/blob/2584b3b1694fb3cc86afa1e63193effb5c356934/pkg/manifests/config.go#L149 https://github.com/openshift/cluster-monitoring-operator/blob/2584b3b1694fb3cc86afa1e63193effb5c356934/pkg/manifests/config.go#L562 https://github.com/openshift/cluster-monitoring-operator/blob/2584b3b1694fb3cc86afa1e63193effb5c356934/pkg/manifests/config.go#L258 @cewong IIUC you want to provide a node selector to the UWM components, AFAIK this can already be done through the configmap in the UWM namespace. E.g: apiVersion: v1 kind: ConfigMap metadata: name: user-workload-monitoring-config namespace: openshift-user-workload-monitoring data: config.yaml: | prometheusOperator: nodeSelector: kubernetes.io/os: "linux" So if I'm not missing anything now the hypershift operator just has to start managing the UWM ConfigMap. With this in mind I'm going to send this bug to the hypershift team, please send it back in case I've missed something. @jmarcal my comment was that this can work if you set these node selectors yourself. So the way I see it, we have 2 options: 1) document that if you want to enable UWM on a hypershift cluster you must set the node selectors in the UWM config so that UWM pods can be scheduled. OR 2) the CMO can modify the default node selector based on the value of infrastructure.status.controlPlaneTopology. If it equals "External", then default to a selector that doesn't include masters. IMHO #2 is a better UX option for end users. @cewong ahh sorry I didn't understood you the first time. I agree with you #2 seems like the best UX, I've implemented that approach to be seen if team approves 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 |