Which chart:
Owncloud v10.2.13
Describe the bug
The existingSecret is not respected for OWNCLOUD_SMTP_PASSWORD and OWNCLOUD_PASSWORD, the charts looks instead for the secret bitnami-owncloud.
|
name: {{ include "common.names.fullname" . }} |
To Reproduce
Steps to reproduce the behavior:
- Use the
existingSecret parameter and do not have a bitnami-owncloud secret in your namespace
- There is a
CreateContainerConfigError
Expected behavior
The deployment template gets the password secrets from .Values.existingSecret when it exists.
To correct
The deployment.yaml should use around lines 130/140 a conditional: if existingSecret exists then grab values from it, otherwise use the bitnami-owncloud secret
Version of Helm and Kubernetes:
- Output of
kubectl version: 1.21.1
Which chart:
Owncloud v10.2.13
Describe the bug
The
existingSecretis not respected forOWNCLOUD_SMTP_PASSWORDandOWNCLOUD_PASSWORD, the charts looks instead for the secretbitnami-owncloud.charts/bitnami/owncloud/templates/deployment.yaml
Line 130 in 6d1999e
To Reproduce
Steps to reproduce the behavior:
existingSecretparameter and do not have abitnami-owncloudsecret in your namespaceCreateContainerConfigErrorExpected behavior
The deployment template gets the password secrets from
.Values.existingSecretwhen it exists.To correct
The
deployment.yamlshould use around lines 130/140 a conditional: ifexistingSecretexists then grab values from it, otherwise use thebitnami-owncloudsecretVersion of Helm and Kubernetes:
kubectl version: 1.21.1