[Enhancement]: ability to use node fqdn for preferredNodePortAddressType #9792
olivierbouffet
started this conversation in
General
Replies: 1 comment 2 replies
-
Strimzi cannot make-up the FGDN for you. If you configure your Kubernetes cluster to have it properly listed in the node status, it will be used. Alternatively, you can override the advertised hostnames using the |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Related problem
Hello,
I am running a bare metal k8s cluster, my nodes are configured with the short name in kubernetes and I want to use : nodeport, externalTrafficPolicy local and a valid SSL certificate for external listener.
I only have InternalIP and Hostname available in node status:
So if I try to set
preferredNodePortAddressType: Hostname
only the shortname will be advertised, and I will not be able to have a valid certificate because my certificate issuer does not accept short hostname.Suggested solution
Would it be possible to add an option to support full hostname (fqdn) for the prefered node port address type.
Alternatives
I can workaround that with externalTrafficPolicy Cluster and forcing the advertised address with the fqdn of the nodes.
But for performance point of view I would like to use externalTrafficPolicy Local.
Thanks in advance
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions