Deploying with Istio

When deploying SonarQube in an Istio service mesh environment, you need to configure fixed ports for Hazelcast communication between application nodes. This is required because Istio's sidecar proxy needs to know all ports in advance for traffic management, security policies, and observability.

By default, SonarQube's Hazelcast cluster uses dynamic port allocation, which conflicts with Istio's requirement for explicit port declarations in service definitions and network policies. To resolve this, you must set fixed ports for the following Hazelcast communication channels:

• applicationNodes.webPort - Used by the Web process for cluster communication
• applicationNodes.cePort - Used by the Compute Engine process for cluster communication

Example configuration:

applicationNodes:

  webPort: 4023   # Web process communication
  cePort: 4024    # Compute Engine process communication

This ensures that Istio can properly route traffic, apply security policies, and provide telemetry for all inter-node communication within the SonarQube cluster.