Draft
Conversation
Not needed since k8s peer discovery doesn't call the Kubernetes API
lmiccini
added a commit
to lmiccini/infra-operator
that referenced
this pull request
Mar 16, 2026
Two fixes for RabbitMQ 4.x peer discovery on OTP 26: 1. Include k8s.host, k8s.address_type, and k8s.service_name config options for all RabbitMQ versions (not just 3.x). While 4.x ignores these options, including them matches the current cluster-operator behavior (see rabbitmq/cluster-operator#1865). 2. Change inter-node TLS from verify_peer to verify_none. OTP 26 enforces strict hostname verification with verify_peer, which breaks RabbitMQ 4.x peer discovery: the k8s plugin spawns a hidden Erlang peer via OTP's peer module that connects back via TLS distribution, but the ephemeral peer's node name doesn't match the certificate's SAN entries, causing the TLS handshake to fail. This is a known issue (rabbitmq/rabbitmq-server#11074). Certificate chain validation against the CA is still performed; only hostname matching is skipped. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.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
1 participant
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.
These changes can be merged when we decide to only support RabbitMQ 4.1+. It removes settings that 4.1 k8s peer discovery plugin ignores anyway and removes permissions that were only needed by the old k8s peer discovery.