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.

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

Support for Kubernetes Ingress with Multiple Istio Gateway Controllers #22400

Open
iusergii opened this issue Mar 23, 2020 · 1 comment
Open

Support for Kubernetes Ingress with Multiple Istio Gateway Controllers #22400

iusergii opened this issue Mar 23, 2020 · 1 comment

Comments

@iusergii
Copy link

@iusergii iusergii commented Mar 23, 2020

Describe the feature request
According to Docs I can use Istio Gateway Controller for standart Kubernetes Ingress using annotation with configured ingressClass. Something like: kubernetes.io/ingress.class: istio.

With multiple gateway setup I'd like to have an option to configure which gateway should processes Ingress objects.

Describe alternatives you've considered
We use multiple gateway for two main reason:

  1. We terminate TLS on AWS Classic Load-Balancer and maintain multiple domains.
  2. Internal / External access.

With first case we can migrate to Network Load-Balancere which is still lacking a lot of configuration from k8s side. Don't see workarounds for second case.

Additional context
We're planning migration to Istio and would like to get rid of current Ingress Controller.

@howardjohn

This comment has been minimized.

Copy link
Member

@howardjohn howardjohn commented Mar 23, 2020

I agree, I think we should add an annotation to select which one is used

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.