Skip to content
This repository has been archived by the owner on Jun 12, 2024. It is now read-only.

Propagate TLS client cert from Draft to Tiller #548

Open
fibonacci1729 opened this issue Feb 28, 2018 · 3 comments
Open

Propagate TLS client cert from Draft to Tiller #548

fibonacci1729 opened this issue Feb 28, 2018 · 3 comments
Assignees
@fibonacci1729
Labels
area/client

Comments

@fibonacci1729
Copy link
Contributor

fibonacci1729 commented Feb 28, 2018 •
edited by bacongobbler
Loading

If Tiller TLS is enabled, currently Draft will not be able to communicate to it.

This issue tracks the work for adding a tls-tiller-cert flag to draft init to propagate the Tiller TLS client certificate to Draft.

See: #544
@fibonacci1729 fibonacci1729 self-assigned this Feb 28, 2018
@fibonacci1729 fibonacci1729 mentioned this issue Feb 28, 2018
Closed
@fibonacci1729 fibonacci1729 changed the title Allow propagating Tiller TLS client cert to draftd Propagate Tiller TLS client cert to Draftd Feb 28, 2018
@squillace
Copy link
Contributor

+1. :-|

@bacongobbler
Copy link
Contributor

oops! accidentally closed this. We still need a way to communicate with a TLS-backed tiller instance.

@bacongobbler bacongobbler reopened this Apr 23, 2018
@bacongobbler bacongobbler changed the title Propagate Tiller TLS client cert to Draftd Propagate TLS client cert from Draft to Tiller Apr 23, 2018
@Sharma-Rajat
Copy link

+1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@fibonacci1729 fibonacci1729

Labels
area/client
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bacongobbler @squillace @fibonacci1729 @Sharma-Rajat