From bf96b295f87c9c83c447ad92bfbb0f0ea1f3dcd4 Mon Sep 17 00:00:00 2001
From: Tobias Trabelsi
 <64127335+tobias-trabelsi-sonarsource@users.noreply.github.com>
Date: Wed, 12 Jan 2022 10:38:44 +0100
Subject: [PATCH] DOCKER-43 additional containers can be specified with DCE
 helm chart now

---
 .../src/pages/setup/sonarqube-cluster-on-kubernetes.md       | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md b/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md
index d276dd03892..8cf6243c2f2 100644
--- a/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md
+++ b/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md
@@ -166,11 +166,6 @@ This documentation only contains the most important Helm chart customizations. S
 
 As SonarQube is intended to be run anywhere, there are some drawbacks that are currently known when operating in Kubernetes. This list is not comprehensive, but something to keep in mind and points for us to improve on.
 
-### No Sidecar Support
-
-There is currently no support for additional sidecar containers.
-If you want to use a sidecar container with the SonarQube deployment, you have to manually alter the deployment.
-
 ### Problems with Azure Fileshare PVC
 
 Currently, there is a known limitation when working on AKS that resonates around the use of Azure Fileshare. We recommend using another storage class for persistency on AKS.
-- 
2.39.5