Sonarqube pods failing due to multiple pod distruption budget

I have deployed sonarqube dce on my EKS cluster version 1.28. Using below commands

helm repo add sonarqube https://SonarSource.github.io/helm-chart-sonarqube
helm repo update
kubectl create namespace sonarqube-dce
export JWT_SECRET=$(echo -n "xxxxxxxx" | openssl dgst -sha256 -hmac "xxxxxxxx" -binary | base64)
helm upgrade --install -n sonarqube-dce sonarqube-dce --set ApplicationNodes.jwtSecret=$JWT_SECRET sonarqube/sonarqube-dce

When I describe the pod I see this error, any help to debug this error would be appreciated.

k describe po sonarqube-sonarqube-dce-search-2

  Type     Reason                        Age                    From               Message
  ----     ------                        ----                   ----               -------
  Normal   Scheduled                     3m1s                   default-scheduler  Successfully assigned sonarqube-dce/sonarqube-sonarqube-dce-search-2 to ip-10-11-111-95.ec2.internal
  Normal   Started                       2m59s                  kubelet            Started container init-sysctl
  Normal   Pulled                        2m59s                  kubelet            Container image "sonarqube:10.4.1-datacenter-app" already present on machine
  Normal   Created                       2m59s                  kubelet            Created container init-sysctl
  Normal   Created                       2m58s                  kubelet            Created container init-fs
  Normal   Pulled                        2m58s                  kubelet            Container image "sonarqube:10.4.1-datacenter-app" already present on machine
  Normal   Started                       2m58s                  kubelet            Started container init-fs
  Warning  MultiplePodDisruptionBudgets  2m53s (x2 over 2m58s)  controllermanager  Pod "sonarqube-dce"/"sonarqube-sonarqube-dce-search-2" matches multiple PodDisruptionBudgets.  Chose "sonarqube-sonarqube-dce-search" arbitrarily.
  Normal   Pulled                        2m53s                  kubelet            Container image "sonarqube:10.4.1-datacenter-search" already present on machine
  Normal   Created                       2m53s                  kubelet            Created container sonarqube-dce-search
  Normal   Started                       2m53s                  kubelet            Started container sonarqube-dce-search
  Warning  MultiplePodDisruptionBudgets  2m52s (x5 over 3m1s)   controllermanager  Pod "sonarqube-dce"/"sonarqube-sonarqube-dce-search-2" matches multiple PodDisruptionBudgets.  Chose "kiali-sonarqube-dce-search" arbitrarily.
  Warning  Unhealthy                     9s (x14 over 2m19s)    kubelet            Startup probe failed:

can someone help

Hey @cloudbud

If you’re using Data Center Edition you surely have access to SonarSource’s Commercial Support. We highly suggest you use that channel, as this community isn’t accustomed to supporting cluster configurations.