-
Notifications
You must be signed in to change notification settings - Fork 627
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 --insecure-connection and --hostname-override flag in node problem detector #24
Conversation
@Random-Liu Not sure if this is related, but I'm getting these logs:
And
I don't know the endpoint in apiserver to look for reported problems. |
@ApsOps Hm, so you set the
Are you able to run heapster with |
@Random-Liu Yes I'm using
I can chat in Kubernetes slack channel if you want me to try any more things :) |
I am closing this pr. There will be a separate pr to solve hostname-override issue. |
Fix #23.
Fix #21.
This PR added 2 node problem detector flags:
--insecure-connection
: This flag will let node problem detector skip TLS verification when talking with apiserver.--hostname-override
: The user could override the host name with this flag. Notice that if you want to override the hostname, you may have to run node problem detector as static pod on each node, and render the flag accordingly with your deployment tool (or manually) to make sure that every node problem detector is properly configured.@sols1 @ApsOps can any of you help me verify the
--insecure-connection
? I don't have a cluster with no admission control in hand. The image version is v0.2.@sols1 @ApsOps @wangyumi
/cc @dchen1107