-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
[Ingress] Support for Mutual TLS with external clients #326
Comments
Hi, |
Issue moved to istio/issues #50 via ZenHub |
zenlint
pushed a commit
to zenlint/istio
that referenced
this issue
Aug 30, 2017
Istio 0.1 announcement blog post.
guptasu
pushed a commit
to guptasu/istio
that referenced
this issue
Jun 11, 2018
kyessenov
pushed a commit
to kyessenov/istio
that referenced
this issue
Aug 13, 2018
Automatic merge from submit-queue. [DO NOT MERGE] Auto PR to update dependencies of mixerclient This PR will be merged automatically once checks are successful. ```release-note none ```
howardjohn
pushed a commit
to howardjohn/istio
that referenced
this issue
Jan 12, 2020
howardjohn
added a commit
to howardjohn/istio
that referenced
this issue
Jan 12, 2020
* Fix release script to read from installer.sha Right now it is just checking out the istio/installer master code, which may not be the right code. * Clean up operator version stuff
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be great to support mutual TLS with Ingress clients.
A working example can be found in nginx ingress controller: https://github.com/kubernetes/ingress/blob/master/controllers/nginx/configuration.md#certificate-authentication
This should not be confused with mutual TLS inside your cluster (i.e. service-to-service communication) -> that's what https://github.com/istio/auth is for.
The text was updated successfully, but these errors were encountered: