Add option for Ingress TLS termination for SolrCloud. #293
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
thelabdude
approved these changes
Jul 21, 2021
…ports in status addresses.
HoustonPutman
changed the title
|
So it looks like Nginx does support tls-passthrough with different TLS options. So while the current PR does work, we will probably want to change a few things to support the ingress TLS termination with Solr TLS enabled. |
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.
Resolves #268
This gives the user to enable TLS Termination in the Ingress for all external Solr traffic.
Users then have the ability to limit what endpoints are available outside the cluster through
hideNodesandhideCommon.This cannot be used with
useExternalAddress, as Solr cannot be listening on HTTP and make internal communication through HTTPS.