Disable insecure port#88
Conversation
|
/assign @s-urbaniak |
|
/assign @ravisantoshgudimetla |
|
/hold |
|
just a small request from my side, I enabled a tls based servicemonitor locally, but the kube-scheduler endpoints seem to point to the wrong port: I believe these should rather be |
In accordance to openshift/cluster-kube-scheduler-operator#88 and openshift/cluster-kube-controller-manager-operator#207 we can now enable TLS for the kube scheduler as well the controller manager.
…le TLS In accordance to openshift/cluster-kube-scheduler-operator#88 and openshift/cluster-kube-controller-manager-operator#207 we can now enable TLS for the kube scheduler as well the controller manager.
0c838c1 to
ed4a0c7
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: s-urbaniak, sttts The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold cancel |
In accordance to openshift/cluster-kube-scheduler-operator#88 we can now enable TLS for the kube scheduler.
…le TLS In accordance to openshift/cluster-kube-scheduler-operator#88 and openshift/cluster-kube-controller-manager-operator#207 we can now enable TLS for the kube scheduler as well the controller manager.
Recently, the control plane switched to secure ports in [1] and [2]. This aligns them in the installer. [1] openshift/cluster-kube-scheduler-operator#88 [2] openshift/cluster-kube-controller-manager-operator#207
…le TLS In accordance to openshift/cluster-kube-scheduler-operator#88 and openshift/cluster-kube-controller-manager-operator#207 we can now enable TLS for the kube scheduler as well the controller manager.
This is blocked by https://github.com/openshift/cluster-monitoring-operator/blob/172beb3e0d2cbf1f79bf61ba9c3f5bea373b4125/assets/prometheus-k8s/service-monitor-kube-scheduler.yaml#L15 pointing to the secure port.