Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[DOC] Improve the hostname verification docs for NodePort listeners #10880

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+7 −2
Open

[DOC] Improve the hostname verification docs for NodePort listeners #10880

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
145dbb9
Improve the hostname verification docs for NodePort listeners
scholzj Nov 25, 2024
ab73c8f
Apply suggestions from code review
scholzj Nov 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions documentation/modules/deploying/con-hostname-verification-node-ports.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@
= Troubleshooting TLS hostname verification with node ports

[role="_abstract"]
Off-cluster access using node ports with TLS encryption enabled does not support TLS hostname verification.
Off-cluster access using node ports with TLS encryption enabled does not support TLS hostname verification.
The reason is that Strimzi does not know what will be the address of the node where the broker Pod will be scheduled and cannot add it to the broker certificate.
scholzj marked this conversation as resolved.
Show resolved Hide resolved
Consequently, clients that perform hostname verification will fail to connect.

For example, a Java client will fail with the following exception:
Expand All @@ -29,4 +30,6 @@ ssl.endpoint.identification.algorithm=
When configuring the client directly in Java, set the configuration option to an empty string:

[source,java]
props.put("ssl.endpoint.identification.algorithm", "");
props.put("ssl.endpoint.identification.algorithm", "");

scholzj marked this conversation as resolved.
Show resolved Hide resolved
Alternatively, if you know the addresses of the worker nodes where the brokers will be scheduled upfront (for example because your cluster is running on bare-metal with a limited number of available worker nodes), you can use the link:{BookURLConfiguring}#property-listener-config-altnames-reference[`alternativeNames` field ^] to add additional SANs to the broker certificates manually.
Loading