Switch api-gateway tls certificate to k8s tls type #443
+5
−4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Chris Wiggins <[email protected]>
|
Hi @chriswiggins thank you so much for your contribution! I'm reviewing and testing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We currently have nginx sitting in front of the api-gateway, doing SSL termination. It is also doing storage proxying, but we can move that to Traefik now with the latest release 😄
We use cert-manager for our certificates, and currently we can't pass a secret cert-manager creates into the api-gateway, as it uses the wrong keys.
We prefer not to use k8's ingress, for a couple of reasons, so want to have Traefik serve the traffic directly