-
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: use SDS, remove preconfigured gateway #22227
Conversation
This makes some improvements to our Ingress support. First, we remove the Gateway installed during install. Then we can fix the autogenerated internal Gateway to "properly" select the correct gateway deployment. This should be configurable, I will add this once we add support for IngressClass. Next, support multiple `tls` blocks, and use SDS to pass these. This aligns great with the Ingress model, where we are pointing to Secrets already. I also had to fix the controller to properly trigger events on Gateway changes. I also extended the tests to include HTTPS calls.
0b1a1d1
to
b501035
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(I reviewed istioctl test changes only).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving no-op istioctl
changes.
@howardjohn do you know under which Istio version will this be released? |
1.6
…On Wed, May 13, 2020, 6:03 AM Guy Rombaut ***@***.***> wrote:
@howardjohn <https://github.com/howardjohn> do you know under which Istio
version will this be released?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#22227 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEYGXJVZMY7WOSWR7ADTRLRRKLBLANCNFSM4LMWDWMA>
.
|
Thanks @howardjohn |
This makes some improvements to our Ingress support. First, we remove
the Gateway installed during install. Then we can fix the autogenerated
internal Gateway to "properly" select the correct gateway deployment.
This should be configurable, I will add this once we add support for
IngressClass.
Next, support multiple
tls
blocks, and use SDS to pass these. Thisaligns great with the Ingress model, where we are pointing to Secrets
already.
I also had to fix the controller to properly trigger events on Gateway
changes.
I also extended the tests to include HTTPS calls.
I recommend we merge #22134 in before this so we can have better testing