-
Notifications
You must be signed in to change notification settings - Fork 667
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 TLS on Gateway #3438
Labels
area/gateway-api
Issues or PRs related to the Gateway (Gateway API working group) API.
kind/feature
Categorizes issue or PR as related to a new feature.
Milestone
Comments
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Mar 11, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Updates projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Mar 12, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Updates projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Mar 12, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Updates projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Apr 1, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Fixes projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Apr 7, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Fixes projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Apr 9, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Fixes projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Apr 9, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Fixes projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Apr 13, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Fixes projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Apr 14, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Fixes projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Apr 15, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Fixes projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Apr 15, 2021
Gateways can now supply certificateRefs which allow the Gateway & it's selected HTTPRoutes to terminate TLS at the Envoy listener. Fixes projectcontour#3438 Signed-off-by: Steve Sloka <slokas@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/gateway-api
Issues or PRs related to the Gateway (Gateway API working group) API.
kind/feature
Categorizes issue or PR as related to a new feature.
A Gateway can define a
GatewayTLSConfig
which allows the TLS bits to defined on the Gateway and not required on the route.//ref: https://gateway-api.sigs.k8s.io/spec/#networking.x-k8s.io/v1alpha1.GatewayTLSConfig
The text was updated successfully, but these errors were encountered: