Use secure port for scheduler and controller-manager liveness probe

[joshrosso]

Feature request:

Since 1.13, kube-controller-manager and kube-scheduler expose secure ports and marked insecure ports as deprecated.

scheduler: kubernetes/kubernetes#69663

change: 1.13
enable secure port: 10259
deprecate old port: 10251

controller-manager: kubernetes/kubernetes#67069

change: 1.12
enable secure port: 10257
deprecate old port: 10252

We should use the secure ports as the default the livenessProbes going forward. I have this fixed in a fork and will open a PR.

Versions

kubeadm version

kubeadm version: &version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.0-alpha.0.1048+21904a5f7d38b1", GitCommit:"21904a5f7d38b1054edad36f3b05b0d7bd556d08", GitTreeState:"clean", BuildDate:"2018-12-18T01:09:09Z", GoVersion:"go1.11.3", Compiler:"gc", Platform:"linux/amd64"}

[luxas]

Closing this as a duplicate of #1285

[rosti]

#1285 was about enabling secure serving, this is about redirecting the liveness probes to the secure ports. As of today, everything in #1285 is done, but the liveness probes are still working with HTTP.
/reopen

[k8s-ci-robot]

@rosti: Reopened this issue.

In response to this:

#1285 was about enabling secure serving, this is about redirecting the liveness probes to the secure ports. As of today, everything in #1285 is done, but the liveness probes are still working with HTTP.
/reopen

Instructions 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.

[rosti]

This one can be thorny - definitely not a good first issue!
/remove-good-first-issue

[yastij]

/assign
/remove-help

[neolit123]

@yastij i've sent a PR for this kubernetes/kubernetes#85043