fix: encode GRAYLOG_HTTP_TLS_KEY_PASSWORD

[monrax]

Summary

Small fix: encode TLS key password secret field

What changed

• Apply b64enc to graylog.config.tls.keyPassword in secrets.yaml

Linked issues

This fixes #67

Checklist

• Tests added/updated
• Documentation updated
• This PR includes a new feature
• This PR includes a bugfix
• This PR includes a refactor

Testing Checklist

Static Validation

• Linter check passes: helm lint ./charts/graylog
• Helm renders local template sucessfully: helm template graylog ./charts/graylog --validate

Installation

• Fresh installation completes successfully: helm install graylog ./charts/graylog
• All pods reach Running state: kubectl rollout status statefulset/graylog
• Helm tests pass: helm test graylog

Functional (if applicable)

• Web UI accessible and login works
• DataNodes visible in System > Cluster Configuration
• Inputs can be created and receive data

Upgrade (if applicable)

• Upgrade from previous release succeeds
• Scaling up/down works correctly
• Configuration changes apply correctly

Specific to this PR

• Verify the following process can be carried out without errors:

  0. Install normally

  helm install graylog ./charts/graylog -n graylog --create-namespace --set graylog.service.type=LoadBalancer

  1. Add my-graylog.local to your /etc/hosts
  2. Generate a new encrypted cert-key pair

  openssl req -newkey rsa:2048 -keyout tls.key -x509 -days 7 -out tls.crt \
    -subj "/CN=my-graylog.local" -addext "subjectAltName = DNS:*.graylog-svc.graylog.svc.cluster.local"

  3. Create a new secret

  kubectl create secret generic my-tls -n graylog --from-file=tls.key --from-file=tls.crt

  4. Perform upgrade

  helm upgrade graylog ./charts/graylog -n graylog --reuse-values \
    --set graylog.config.tls.enabled=true \
    --set graylog.config.tls.secretName=my-tls \
    --set graylog.config.tls.updateKeyStore=true \
    --set graylog.config.tls.keyPassword=hunter2

Notes for reviewers

• Verify all tests above pass
• Sync up with the author before merging
• The commit history should be preserved - use rebase-merge or standard merge options when applicable