Password set with existingSecret not working

[gianmarco-mameli]

Hi,
I've deployed this chart on a k3s instance, all works as expected except the admin password configured as external secret.
If I use the value adminPassword it works, but with this snippet in the values:

  admin:
    enabled: true
    existingSecret: "pihole-password"

and the secret configured like this

Name:         pihole-password
Namespace:    pihole
Labels:       <none>
Annotations:  <none>

Type:  Opaque

Data
====
password:  6 bytes

doesn't work

What am I doing wrong?
Thanks

[1moere1]

same issue here

[Robsta86]

Same issue here. I see the pod has the correct value from the secret set for the environment variable called "WEBPASSWORD", so helm configuration wise things seem to do what they should be doing.

Maybe a bug in pi-hole?

[gianmarco-mameli]

Hi, I made it work, the only difference is that I'm not inserting the secret directly, but it's generated from a third party secret injector (1Password Operator), so I think the difference it's in the encoding of the value.

Chart version: v2.27.0
In the values file I have this config:

admin:
  enabled: true
  existingSecret: "pihole-password"
passwordKey: "password"

[polfor]

Same issue here on chart v2.29.1
I have my secret base64 encoded then using a manifest encrypted with sops (age). When describing the secret its value is correctly decrypted, so kinda clueless.

admin:
         enabled: true
         existingSecret: pihole-admin-password
         passwordKey: "password"

[xalxnder]

Same issue for me on chart v2.31.0.

[m00dawg]

I might be doing something wrong. pi-hole in k8s is very new to me, but my local yaml is this:

# create a kubernetes service and expose
# port 53 outside of cluster on the local network
serviceDns:
  type: LoadBalancer
  annotations:
    metallb.io/loadBalancerIPs: 192.168.100.77
    metallb.io/allow-shared-ip: pihole-svc

serviceTCP:
  type: LoadBalancer
  annotations:
    metallb.io/loadBalancerIPs: 192.168.100.77
    metallb.io/allow-shared-ip: pihole-svc

serviceUDP:
  type: LoadBalancer
  annotations:
    metallb.io/loadBalancerIPs: 192.168.100.77
    metallb.io/allow-shared-ip: pihole-svc

serviceWeb:
#  loadBalancerIP: 192.168.100.77
  type: LoadBalancer
  annotations:
    metallb.io/loadBalancerIPs: 192.168.100.77
    metallb.io/allow-shared-ip: pihole-svc

persistentVolumeClaim:
  enabled: true
  storageClass: "longhorn"

podDnsConfig:
  enabled: true
  policy: "None"
  nameservers: [127.0.0.1, 192.168.100.2, 192.168.100.17]

adminPassword: "<redacted>"

However, this doesn't seem to set the actual password when I look at helm status or try to login via the admin interface. It sounded semi-related to this bug so thought I'd offer up my $0.02 to it. Apologies if this ends up being unrelated.

Side-note, my custom nameservers also don't seem to be getting applied.