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

Consider exposing the ability to route both HTTP and HTTPS traffic to a cloud.Service #502

Closed
pgavlin opened this issue May 31, 2018 · 1 comment
Closed

Consider exposing the ability to route both HTTP and HTTPS traffic to a cloud.Service #502

pgavlin opened this issue May 31, 2018 · 1 comment
Assignees
@lukehoban
Labels
kind/enhancement Improvements or new features resolution/wont-fix This issue won't be fixed

Comments

@pgavlin
Copy link
Member

pgavlin commented May 31, 2018

e.g. by using multiple load balancer listeners. The target container can then set policy based on the origin of the connection.
@pgavlin pgavlin added this to the 0.15 milestone May 31, 2018
@joeduffy
Copy link
Member

joeduffy commented Jun 8, 2018

I think we already have a workaround for this with tcp vs http. We can of course revisit doing better, but I think we have enough on our plates for launch at the moment.

@joeduffy joeduffy modified the milestones: 0.15, 0.16 Jun 8, 2018
@lukehoban lukehoban modified the milestones: 0.16, 0.18 Jul 12, 2018
@lukehoban lukehoban modified the milestones: 0.18, 0.19 Sep 10, 2018
@lukehoban lukehoban modified the milestones: 0.19, 0.20 Oct 25, 2018
@joeduffy joeduffy changed the title Consider exposing the ability to route both HTTP and HTTPS traffic to a cloud.Service. Consider exposing the ability to route both HTTP and HTTPS traffic to a cloud.Service Oct 29, 2018
@lukehoban lukehoban mentioned this issue Nov 8, 2018
Closed
@lukehoban lukehoban modified the milestones: 0.20, 0.22 Dec 7, 2018
@lukehoban lukehoban removed this from the 0.22 milestone Mar 17, 2019
@lukehoban lukehoban added the kind/enhancement Improvements or new features label Jul 24, 2023
@mjeffryes mjeffryes added the resolution/wont-fix This issue won't be fixed label Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lukehoban lukehoban

Labels
kind/enhancement Improvements or new features resolution/wont-fix This issue won't be fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lukehoban @mjeffryes @pgavlin @joeduffy