Draft
Conversation
Signed-off-by: Raúl Zamora Martínez <76525382+zmraul@users.noreply.github.com>
This file contains hidden or 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.
Solves #424 for 4 track
Introduces a new boolean config option
certificate_include_ip_sansthat defaults to false. This config also forces the cluster to switch to dns based hostnames (otherwise remote apps won't be able to verify Kafka certificates when TLS is enabled)TODO
setup_internal_tlsflow. When IPs are disabled from the cluster via config, the internal tls setup that uses IP based certificates becomes obsolete. The nodes fail to verify the internal certificates.