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

DestinationRule: TLS policy for different ports #449

Closed
costinm opened this issue Apr 13, 2018 · 2 comments
Closed

DestinationRule: TLS policy for different ports #449

costinm opened this issue Apr 13, 2018 · 2 comments
Assignees
@rshriram @louiscryan

Comments

@costinm
Copy link
Contributor

costinm commented Apr 13, 2018

If service foo has multiple ports, some may have their own (M)TLS in app space, some may be clear text and some may want to have Istio MTLS added.

Right now I don't think this can be expressed in the API - except by making some decisions based on the port name ( which I don't think we do in the implementation ).
@rshriram
Copy link
Member

its a TODO. I even had a PR opened for this a while ago and then closed it as I didn't have time to get to it.. let me dig it up and reopen the PR

@rshriram
Copy link
Member

solved by #450

incfly pushed a commit to incfly/api that referenced this issue Jun 13, 2018
@qiwzhang
Update to mixerclient with new check cache. (istio#449)
ad8c45b 
* Update to mixerclient with new check cache.

* update README
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rshriram rshriram

@louiscryan louiscryan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@costinm @rshriram @louiscryan