Allow the program to run without TLS #1
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
added 2 commits
November 4, 2016 14:02
… a kubernetes cluster. (Ingress doesn't support HTTPS on the backend, only on the front.)
skippie81
pushed a commit
to skippie81/kubernetes-ldap
that referenced
this pull request
Dec 30, 2017
Merge pull request apprenda-kismatic#1 from rajatjindal83/master
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.
In my environment, I want to run kubernetes-ldap in a container, inside the cluster. That means I define a service and ingress for it, so users have a public https URL they can use. The ingress spec supports SSL on the front end, but not on the back end. So it has to connect to kubernetes-ldap via in-cluster HTTP.