-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add liveness and readiness probes to static pod #77
Conversation
/hold Waiting for 1.12.2 rebase and controller manager that have secure healthz endpoint. |
c6f88cc
to
4b3e594
Compare
/hold cancel |
789dae8
to
9062404
Compare
@@ -9,8 +9,8 @@ extendedArguments: | |||
- "/etc/kubernetes/secrets/kube-ca.crt" | |||
cluster-signing-key-file: | |||
- "/etc/kubernetes/secrets/kube-ca.key" | |||
port: | |||
- "0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
scheme: HTTPS | ||
port: 10257 | ||
path: healthz | ||
initialDelaySeconds: 45 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copied from kube-apiserver, i'm up for suggestion on better numbers (i think we need some initial delay till the controller manager apiserver boots up)
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mfojtik, sttts The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
@deads2k @sttts lets discuss the probes under this PR...
Right now, we have wrong port on the service and I don't think so we serving the healthz or metrics security from controller manager. Also the
10252
seems odd and we need to decide if we keep it or just move to something else? (8444 before).