Securing behind a proxy

It is recommended to run SonarQube behind a proxy if it should be accessible from outside.

As a DCE subscriber, Sonar will assist with the setup and configuration of your cluster. Get in touch with your account manager to receive appropriate onboarding resources.

With the Data Center Edition, you’ll need a load balancer to balance HTTP requests (load) between the application nodes configured in the cluster (see also Installation requirements #Load balancer). You can configure the load balancer as a reverse proxy. See Securing behind a proxy.

If you deploy SonarQube on Kubernetes, you’ll need an ingress controller. An ingress controller is a specialized load balancer for Kubernetes that acts as a reverse proxy and manages traffic routing to services within the Kubernetes cluster. See Customizing Helm chart #Creating an Ingress to make SonarQube Server service accessible from outside.

Related pages

• Elasticsearch security features

• Network rules