Charts: [stable/traefik] Support mutual TLS authentication

Created on 9 Dec 2018  路  9Comments  路  Source: helm/charts

Is this a request for help?:


Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST

Version of Helm and Kubernetes:

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-04T07:51:55Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:25:46Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

$ helm version
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}

Which chart: stable/traefik

What happened: Unable to configure traefik to enable mutual TLS authentication

What you expected to happen: The chart should provide the ability to enable and configure mTLS

How to reproduce it (as minimally and precisely as possible):

  1. Deploy traefik
  2. Deploy a HTTPS web server that echoes received headers back to the client, such as echoheaders
  3. Access the web server, providing a client certificate: curl --cert tls.crt --key tls.key https://myserver.example.com
  4. Notice there is no "x-forwarded-tls-client-cert" header in the returned response body
  5. Notice that it is possible to access the web server without using mTLS: curl https://myserver.example.com

Anything else we need to know:
No

lifecyclstale

Most helpful comment

Created PR #9829 for this

All 9 comments

Created PR #9829 for this

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

Was just about to make a PR for this work. Would be great to get this merged soon.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@tlmiller, @justurm PR #9829 didn't get any attention and, since we (in the project I am working on) have now decided to stay with nginx, I will not pursue this further.

If either of you would like to pick this up then be my guest and please don't hesitate to give me a shout if I can do anything to help.

@somcsel cheers, I will see if I can get it over the line. Would love to have this to support some legacy apps.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

This issue is being automatically closed due to inactivity.

New PR for this issue #13347

Was this page helpful?
0 / 5 - 0 ratings