You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat(helm): add extraObjects support for external secret management
- Add extraObjects configuration field to values.yaml
- Create templates/extra-objects.yaml to render additional manifests
- Update README.md with usage examples for ExternalSecretOperator and SealedSecrets
- Add automated tests in tests/extra_objects_test.yaml
- Enable GitOps-friendly secret management by allowing injection of custom resources
Signed-off-by: Ralf Dahmen <ralf.dahmen14@googlemail.com>
### Install with extraObjects for external secret management
121
+
122
+
You can inject additional Kubernetes manifests using the `extraObjects` configuration. This is particularly useful for GitOps scenarios where you want to manage secrets externally using tools like ExternalSecretOperator or SealedSecrets.
123
+
124
+
The `extraObjects` field accepts an array of raw YAML strings rendered alongside the Temporal chart. Each entry supports Go templating (e.g. `{{ .Release.Name }}`).
125
+
126
+
#### Example with ExternalSecretOperator
127
+
128
+
```yaml
129
+
extraObjects:
130
+
- |
131
+
apiVersion: external-secrets.io/v1beta1
132
+
kind: ExternalSecret
133
+
metadata:
134
+
name: {{ .Release.Name }}-db-secret
135
+
spec:
136
+
secretStoreRef:
137
+
name: aws-secretsmanager
138
+
kind: SecretStore
139
+
target:
140
+
name: {{ .Release.Name }}-db-secret
141
+
creationPolicy: Owner
142
+
data:
143
+
- secretKey: password
144
+
remoteRef:
145
+
key: prod/temporal/db
146
+
property: password
147
+
```
148
+
149
+
150
+
#### Example with SealedSecrets
151
+
152
+
```yaml
153
+
extraObjects:
154
+
- |
155
+
apiVersion: bitnami.com/v1alpha1
156
+
kind: SealedSecret
157
+
metadata:
158
+
name: {{ .Release.Name }}-db-secret
159
+
spec:
160
+
encryptedData:
161
+
password: <encrypted-password>
162
+
template:
163
+
metadata:
164
+
name: {{ .Release.Name }}-db-secret
165
+
```
166
+
120
167
### Install with MySQL
121
168
122
169
To use a MySQL database, copy the [MySQL values file](values/values.mysql.yaml) locally and edit it with your database connection details:
0 commit comments