switch controller manager to secure port#207
switch controller manager to secure port#207openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
662f92b to
4d54ada
Compare
|
/lgtm |
4d54ada to
57a1bfa
Compare
|
New changes are detected. LGTM label has been removed. |
|
adding lgtm back, fixed the liveness probe port |
|
/retest |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mfojtik, soltysh, 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 |
|
/retest |
|
/hold |
|
/hold cancel |
|
/assign @s-urbaniak This also needs a change on the monitoring side. |
|
/cc @s-urbaniak |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
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.
|
/retest |
In accordance to openshift/cluster-kube-controller-manager-operator#207 we can now enable TLS for 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.
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.
Rebase landed, we should switch the port to secure again. This updates controller manager default config and set the insecure port to 0 and also update the init container to check the secure port.
Also sets the
cert-dirto/var/run/kubernetes.