Skip to content
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

Can add a insecure port listen on local ip for healthcheck #8226

Closed
helinbo2015 opened this issue Jul 7, 2017 · 1 comment
Closed

Can add a insecure port listen on local ip for healthcheck #8226

helinbo2015 opened this issue Jul 7, 2017 · 1 comment
Assignees

Comments

@helinbo2015
Copy link

i have met a case that if etcd http(s) server has a insecure port, it may helps a lot.

  1. In my kubernetes env(use kubelet's static pod to start master's components(include ETCD)), deployed ETCD with tls.
  2. use kubelet's readinessprobe httpGet funciton to check the health status of ETCD on the same vm.
    the problem is: the readinessprobe httpGet function is not support https scheme, so this way is not work.

now, the workaround is: add a health check script(curl with tls) and tls files in the ETCD image, and use kubelet readinessprobe Cmd function to exec the health check script.
As you see, This is not a indirect way for ETCD component that supports REST API well.

@hexfusion
Copy link
Contributor

hexfusion commented Jul 11, 2017

now, the workaround is: add a health check script(curl with tls) and tls files in the ETCD image, and use kubelet readinessprobe Cmd function to exec the health check script.
As you see, This is not a indirect way for ETCD component that supports REST API well.

@helinbo2015 I am not sure if I am completely understanding your use case. But if you are deploying etcd in k8s using tls perhaps you should look at the way etcd-operator does this with secrets. Although this doesn't eliminate the "tls file" dependency perhaps it streamlines it when using curl with tls for your probe?

-HTH

https://github.com/coreos/etcd-operator/blob/master/doc/user/cluster_tls.md

@heyitsanthony heyitsanthony added this to the v3.3.0-maybe milestone Jul 18, 2017
@gyuho gyuho removed this from the v3.3.0-maybe milestone Nov 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants