-
Notifications
You must be signed in to change notification settings - Fork 130
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
WIP: Replace readyz sidecar container with etcds own probes #1321
WIP: Replace readyz sidecar container with etcds own probes #1321
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jubittajohn The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: jubittajohn <[email protected]>
9e5ac8c
to
2cf5c88
Compare
port: 9980 | ||
path: readyz | ||
port: 2379 | ||
path: readyz?exclude=data_corruption&exclude=linearized_read | ||
scheme: HTTPS |
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.
I think it's failing on:
{"level":"warn","ts":"2024-08-20T03:55:49.588638Z","caller":"embed/config_logging.go:169","msg":"rejected connection","remote-addr":"10.0.36.39:41140","server-name":"","error":"tls: client didn't provide a certificate"}
since we can't supply mTLS certs in the probe configs, we could try to split the http server out with the etcd args:
--listen-client-http-urls=
dunno if we can simply take on the ":2378" port for starters and then see if we still need some form of mTLS along with it.
(just checking something for another ticket - don't be confused) /override ci/prow/e2e-aws-etcd-recovery |
@tjungblu: Overrode contexts on behalf of tjungblu: ci/prow/e2e-aws-etcd-recovery In response to this:
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-sigs/prow repository. |
@jubittajohn: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
PR needs rebase. 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-sigs/prow repository. |
let's shelve this until we have a solution for /close |
@tjungblu: Closed this PR. In response to this:
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-sigs/prow repository. |
No description provided.