Bug 1871855

Summary: user workload monitoring: remove --kubelet-service setting
Product: OpenShift Container Platform Reporter: Sergiusz Urbaniak <surbania>
Component: MonitoringAssignee: Sergiusz Urbaniak <surbania>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.6CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:31:27 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 Sergiusz Urbaniak 2020-08-24 13:06:01 UTC
Currently, the user workload monitoring prometheus-operator has the `--kubelet-service` setting enabled.

This setting is unnecessary and actually not wanted as it auto-creates kubelet endpoints and services.

We have to disable it.

Steps to reproduce:
1. Enable user workload monitoring

2. Invoke
$ oc -n openshift-user-workload-monitoring get deployment -o yaml | less
...
      spec:
        containers:
        - args:
          - --kubelet-service=kube-system/kubelet
...


Expected:
No `--kubelet-service` setting is added to the user workload monitoring prometheus-operator deployment.

Comment 3 Junqi Zhao 2020-08-26 07:32:13 UTC
issue is fixed with 4.6.0-0.nightly-2020-08-25-234625
# oc -n openshift-user-workload-monitoring get deployment prometheus-operator -o yaml | grep "kubelet-service"
no result

Comment 5 errata-xmlrpc 2020-10-27 16:31:27 UTC
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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196