Bug 1809207 - ServiceMonitor for kubelet shouldn't be provided by cluster-monitoring-operator
Summary: ServiceMonitor for kubelet shouldn't be provided by cluster-monitoring-operator
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: Pawel Krupa
QA Contact: Junqi Zhao
Depends On:
TreeView+ depends on / blocked
Reported: 2020-03-02 15:14 UTC by Pawel Krupa
Modified: 2020-03-19 07:22 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-03-19 07:22:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Pawel Krupa 2020-03-02 15:14:36 UTC
Description of problem:
CMO shouldn't own ServiceMonitor for kubelet. Additionally kubelet should expose metrics over secure channel instead of plain HTTP.

Version-Release number of selected component (if applicable):
4.4 (possibly also earlier versions)

How reproducible:

Steps to Reproduce:
1. Start a cluster
2. Go to prometheus UI
3. Check connection schema for kubelet

Actual results:
Metrics are exposed over HTTP connection and kubelet is registered as part of openshift-monitoring namespace

Expected results:
Metrics are exposed over HTTPS connection and kubelet is not governed by cluster-monitoring-operator

Additional info:
TLS config can be modeled after API server operator ServiceMonitor definition: https://github.com/openshift/cluster-openshift-apiserver-operator/blob/master/manifests/0000_90_openshift-apiserver-operator_03_servicemonitor.yaml

Note You need to log in before you can comment on or make changes to this bug.