You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by "Edeholland (via GitHub)" <gi...@apache.org> on 2025/03/09 21:47:55 UTC
[I] Using secretName doesn't pass helm validation [incubator-devlake-helm-chart]
Edeholland opened a new issue, #325:
URL: https://github.com/apache/incubator-devlake-helm-chart/issues/325
I have the following spec for my helmrelease;
```
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
name: devlake
namespace: devlake
spec:
releaseName: devlake
targetNamespace: devlake
storageNamespace: devlake
chart:
spec:
chart: devlake
sourceRef:
kind: HelmRepository
name: devlake
namespace: flux-system
values:
lake:
encryptionSecret:
secretName: devlake-encryption-secret
```
The secret exists and has content:
```
kubectl get secrets
NAME TYPE DATA AGE
devlake-encryption-secret Opaque 1 8m51s
```
However, helm refuses to install because `lake.encryptionSecret.secret.` isn't set:
```
kubectl get helmreleases.helm.toolkit.fluxcd.io devlake
NAME AGE READY STATUS
devlake 113m False Helm upgrade failed for release devlake/devlake with chart devlake@1.0.1: execution error at (devlake/templates/validate.yaml:2:4): Helm test requires lake.encryptionSecret.secret....
```
I want to refer to the secret, not set a hardcoded secret. Is this a bug in the validation or am I missing something?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@devlake.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Using secretName doesn't pass helm validation [incubator-devlake-helm-chart]
Posted by "zjaco13 (via GitHub)" <gi...@apache.org>.
zjaco13 commented on issue #325:
URL: https://github.com/apache/incubator-devlake-helm-chart/issues/325#issuecomment-2730716160
If you have the secret already created, set lake.autoCreateSecret to false and it should deploy successfully.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org