Kestra Helm chart: basicAuth settings not applied in Kubernetes deployment

[ReLoutre]

Describe the issue

Tested Environment:

• Cluster: Local Minikube
• Tools: Helm + kubectl
• OS: [Ubuntu 22.04]

Reproduction steps:

1️⃣ Docker setup: (May be skipped) Since Docker requires root on my system, I enabled user access with:

sudo usermod -aG docker $USER && newgrp docker

2️⃣ Start Minikube:

minikube start

3️⃣ Prepare Helm:

helm repo add kestra https://kestra-io.github.io/helm-charts
helm repo update

4️⃣ Create kestra-values.yaml:

kestra:
  configuration:
    kestra:
      server:
        basic-auth:
          enabled: true

Tested by adding hard coded values for a basic user without notyfing any difference ;

          users:
            - username: admin
              password: changeme

5️⃣ Install Kestra with Helm:

helm install kestra kestra/kestra -f kestra-values.yaml

6️⃣ Expose the service locally:

kubectl port-forward svc/kestra-service 8080:8080

---

Observed behavior: I am able to access the Kestra Web UI at http://localhost:8080 without any Basic Auth prompt. There is also no Kestra popup or prompt suggesting that I should secure the instance (which normally appears when Basic Auth isn’t configured).

---

Expected behavior: With basic-auth.enabled: true in the Helm values, I expect:

• The Web UI to require Basic Auth immediately on access.
• If misconfigured, at minimum, a popup or alert within the UI prompting me to secure the instance.

---

Conclusion: It seems the basicAuth configuration is ignored or not applied properly in this setup. I can reproduce this consistently with a fresh Minikube + Helm install.

Environment

Firefox

[ReLoutre]

According to another user : Basic Auth configuration within the UI does not persist. Wasn't able to reproduce since there is no auth at all for me.

[joshuarestivo]

I'm able to manage the basic auth configuration in the UI via Administration -> Stats -> Activate Basic Authentication. It activates for me and works until I delete / redeploy the pod. Then, it must be manually configured again.

[imdmahajankanika]

Hello! I am also getting the same issue

I need to put manually below config in kestra-secret under application-k8s.yml to make it work. But there is no track of it in helm values.

kestra:
  url: https://KESTRA_URL
  server:
    basic-auth:
      enabled: true
      username: 
      password