serviceMonitorKubeScheduler: enable TLS#312
Conversation
In accordance to openshift/cluster-kube-scheduler-operator#88 we can now enable TLS for the kube scheduler.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: s-urbaniak 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 |
openshift-ci-robot
added
approved
|
xref #308 |
|
blocked by openshift/cluster-kube-scheduler-operator#89 |
|
/retest |
|
/retest |
|
@s-urbaniak: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
missing permissions in scheduler tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1697875 |
|
closing in favor of #316 |
2 participants
In accordance to
openshift/cluster-kube-scheduler-operator#88 we can
now enable TLS for the kube scheduler.
This is the second part of securing the control plane.
This PR will most likely fail until the
cluster-kube-scheduler-operator PR is present in the build images.