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.

Sign up for GitHub

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

Jump to bottom

Kubernetes can no longer use TLS for etcd #21051

Closed
danderson opened this issue Feb 11, 2016 · 3 comments
Closed

Kubernetes can no longer use TLS for etcd #21051

danderson opened this issue Feb 11, 2016 · 3 comments
Labels
sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@danderson
Copy link

I hope I'm just missing something, but a grep of source code seems to confirm that I'm not...

Kubernetes 1.1 supported using TLS for the connection to etcd, via the deprecated etcd client. With 1.2alpha, it seems that this has been lost in the migration to the supported etcd client.

To be more specific: there's no way to specify a certificate for client authentication, or to specify a non-systemwide CA certificate to authenticate the Etcd server.

This is a pretty serious regression. Please fix.
@roberthbailey roberthbailey added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Feb 11, 2016
@adohe-zz
Copy link

@danderson I will open a PR to fix this as soon as possible.

@maclof
Copy link
Contributor

maclof commented Feb 11, 2016

There is already an issue open for this #18760

@lavalamp
Copy link
Member

Yup, let's discuss in #18760

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@danderson @lavalamp @adohe-zz @maclof @roberthbailey