Service ports are not accessible with IPv6

Solace Event Broker
1

Hi! I’m trying to run a dev-setup of the event broker in an IPv6-only kubernetes cluster using the helm-chart provided at GitHub - SolaceProducts/pubsubplus-kubernetes-helm-quickstart: Quickstart to launch a Solace PubSub+ Software Event Broker in Kubernetes using Helm.
Unfortunately, I’m not able to connect to the service-ports from any of the other pods, with the exception of port 8080 and port 2222. I logged into the message broker pod and noticed that the ports managed by the the dataplane process are only opened for IPv4:

[appuser@solace-pubsubplus-0 sw]$ lsof -nP -iTCP -sTCP:LISTEN
COMMAND   PID    USER   FD   TYPE    DEVICE SIZE/OFF NODE NAME
sempmanag 414 appuser   21u  IPv4 691098765      0t0  TCP 127.0.0.1:1025 (LISTEN)
dataplane 549 appuser   41u  IPv4 691090350      0t0  TCP *:55555 (LISTEN)
dataplane 549 appuser   42u  IPv4 691090351      0t0  TCP *:55003 (LISTEN)
dataplane 549 appuser   43u  IPv4 691090352      0t0  TCP *:8008 (LISTEN)
dataplane 549 appuser   44u  IPv4 691090353      0t0  TCP *:5550 (LISTEN)
dataplane 549 appuser   45u  IPv4 691090354      0t0  TCP *:1883 (LISTEN)
dataplane 549 appuser   46u  IPv4 691090355      0t0  TCP *:8000 (LISTEN)
dataplane 549 appuser   47u  IPv4 691090356      0t0  TCP *:9000 (LISTEN)
dataplane 549 appuser   49u  IPv4 691099970      0t0  TCP *:5672 (LISTEN)
sshd      575 appuser    3u  IPv4 691090383      0t0  TCP *:2222 (LISTEN)
sshd      575 appuser    4u  IPv6 691090385      0t0  TCP *:2222 (LISTEN)
nginx     610 appuser    3u  IPv4 691091270      0t0  TCP *:8080 (LISTEN)
nginx     610 appuser    4u  IPv6 691091271      0t0  TCP *:8080 (LISTEN)
nginx     618 appuser    3u  IPv4 691091270      0t0  TCP *:8080 (LISTEN)
nginx     618 appuser    4u  IPv6 691091271      0t0  TCP *:8080 (LISTEN)
lttng-ses 654 appuser   63u  IPv4 691098591      0t0  TCP 127.0.0.1:5345 (LISTEN)

I have looked at the documented configuration options, but found nothing that was related to the IP address family.

Is there a way to make the message broker listen on IPv6?

Thanks!

2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Looking through the documentation, I don’t find any explicit information about IPv6 support for software event broker deployments in Kubernetes.

The documentation discusses various networking and connectivity aspects for Kubernetes deployments, including:

  1. Load balancer configurations
  2. NodePort configurations
  3. Network protocols and ports
  4. Public and private endpoints
  5. Management and messaging connectivity

However, there is no specific mention of IPv6 support or configuration options.

To get accurate information about IPv6 support, I recommend checking:

Since IPv6 support is not explicitly documented, you should consult the Solace documentation for the most up-to-date information about networking capabilities and requirements.