Update development environment to use ingress and TLS. #1935
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
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.
Includes a new dependency on mkcert too.
Description of the change
To further investigate other authproxy options (for #1933) I need a quick, reliable setup with a TLS frontend. This setup uses kind's newer ability to do ingress (together with nginx ingress controller. The mkcert tool is pretty useful too (as all certs that it makes are trusted locally).
Benefits
Can continue #1933 as well as benefit from a TLS setup locally.
Possible drawbacks
Requires port 443 to be available locally (I could perhaps look at adjusting the ingress to use a higher-range port) to map to the kind container.