Skip to content

Commit

Permalink
Update example to use external secrets for MinIO env vars (#587)
Browse files Browse the repository at this point in the history
  • Loading branch information
nitisht authored Apr 19, 2021
1 parent 671d0e0 commit 8373953
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 1 deletion.
9 changes: 9 additions & 0 deletions examples/tenant.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -181,6 +181,15 @@ spec:
# value: "off" # to turn-off browser
# - name: MINIO_STORAGE_CLASS_STANDARD
# value: "EC:2"
# ## For secure env vars like passwords, create an opaque Kubernetes secret and specify the secret in
# ## the `valueFrom` field. The `valueFrom` object must contain the following fields:
# ## `name` - the secret from which MinIO extracts the password, `key` - the data field
# ## within secret, whose value will be set to the env variable's value
# - name: MINIO_IDENTITY_LDAP_LOOKUP_BIND_PASSWORD
# valueFrom:
# secretKeyRef:
# name: ldap-minio-secret
# key: MINIO_IDENTITY_LDAP_LOOKUP_BIND_PASSWORD

## PriorityClassName indicates the Pod priority and hence importance of a Pod relative to other Pods.
## This is applied to MinIO pods only.
Expand Down
2 changes: 1 addition & 1 deletion pkg/apis/minio.min.io/v2/types.go
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ type TenantSpec struct {
CredsSecret *corev1.LocalObjectReference `json:"credsSecret,omitempty"`
// *Optional* +
//
// If provided, the MinIO Operator the specified environment variables when deploying the Tenant resource.
// If provided, the MinIO Operator adds the specified environment variables when deploying the Tenant resource.
// +optional
Env []corev1.EnvVar `json:"env,omitempty"`
// *Optional* +
Expand Down

0 comments on commit 8373953

Please sign in to comment.