Skip to main content
This guide explains how to configure per-pod networking for PulsarBroker using networking.podService and advertisedListeners.

Overview

Two features work together to enable per-pod access: Use cases:
  • Istio Federation / Multi-cluster communication
  • Direct pod access scenarios

Configuration

Example

Add the following to your Helm values.yaml:
Then apply with:

Configuration Reference

networking.podService

advertisedListeners

Use a non-default port (e.g., 6660) to avoid conflict with the default brokerServicePort (6650).

Verify Configuration

Check Created Services

Expected output:

Verify Service Selector

Expected: {"statefulset.kubernetes.io/pod-name":"pulsar-broker-0"}

Test Connectivity