-
Notifications
You must be signed in to change notification settings - Fork 347
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 simple TLS termination #471
Labels
kind/enhancement
New feature or request
provider/kubernetes
Issues related to the Kubernetes provider
Milestone
Comments
arkodg
added
kind/enhancement
New feature or request
provider/kubernetes
Issues related to the Kubernetes provider
labels
Sep 29, 2022
Oof you're right, I was thinking that this was already working end-to-end but yeah the provider is not passing secrets. |
this would have been an easy win for 0.2.0 . This can be considered a bug and added to the 0.2.0 milestone cc @danehans |
arkodg
added a commit
to arkodg/gateway
that referenced
this issue
Sep 30, 2022
Relates to envoyproxy#471 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
arkodg
added a commit
to arkodg/gateway
that referenced
this issue
Sep 30, 2022
Relates to envoyproxy#471 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
arkodg
added a commit
that referenced
this issue
Oct 3, 2022
* xds-translator tests for simple tls Relates to #471 Signed-off-by: Arko Dasgupta <arko@tetrate.io>
This was referenced Oct 7, 2022
the TLS termination conformance tests should be incorporated once they are added upstream which is being tracked with kubernetes-sigs/gateway-api#1104 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/enhancement
New feature or request
provider/kubernetes
Issues related to the Kubernetes provider
Description:
Add support for HTTPS/TLS termination
Examples shown here https://gateway-api.sigs.k8s.io/v1alpha2/guides/tls/#examples
Looks like most of the work is already done in gateway-api translator
gateway/internal/gatewayapi/translator.go
Line 52 in 8e1e981
The text was updated successfully, but these errors were encountered: