From 1e6b9190f9b92431f22be64d54421bbacf05d505 Mon Sep 17 00:00:00 2001 From: duynguyen Date: Mon, 27 Apr 2026 22:10:29 +0700 Subject: [PATCH] fix: update SonarQube monitoring passcode configuration --- manifest/sonarqube/values.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/manifest/sonarqube/values.yaml b/manifest/sonarqube/values.yaml index 1564a90..5236172 100644 --- a/manifest/sonarqube/values.yaml +++ b/manifest/sonarqube/values.yaml @@ -442,8 +442,8 @@ jvmCeOpts: "" # not setting the monitoring passcode will result in a deployment that will never be ready # monitoringPasscode: "define_it" # Alternatively, you can define the passcode loading it from an existing secret specifying the right key -# monitoringPasscodeSecretName: "pass-secret-name" -# monitoringPasscodeSecretKey: "pass-key" +monitoringPasscodeSecretName: "sonarqube-monitoring-passcode" +monitoringPasscodeSecretKey: "monitoringPasscode" ## Environment variables to attach to the pods ##