-
Notifications
You must be signed in to change notification settings - Fork 24
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
Make etcd service more Istio-friendly #108
Conversation
/hold |
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
/hold cancel |
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.
/approve
LGTM label has been added. Git tree hash: 4ca437322826e2f9d40a018f98c9db7a23130c61
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: embik, xrstf 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 |
I tried to set up kcp in a namespace that has istio injection enabled. Unfortunately, it wasn't working (mainly kcp couldn't talk to etcd over the istio-proxy connection) and threw some obscure error messages suggesting authentication failed.
The problem was actually that Istio couldn't detect the right protocol to proxy. I'm adding the
appProtocol
field to both service ports to ensure that Istio knows it has to proxy HTTPS. In addition, the (client) certificates needed to have127.0.0.6
(the istio-proxy sidecar IP) injected so they'd be accepted by the servers. This PR therefore also adds the option to add more ip addresses to the generated certificates.