[bitnami/mongodb-sharded] Fix incorrect nindent in volumePermissions

Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@vmware.com>
This commit is contained in:
Javier J. Salmeron Garcia
2019-11-08 17:43:15 +01:00
parent 9f3eaf7dae
commit 8982222313
3 changed files with 3 additions and 3 deletions

View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: mongodb-sharded
version: 0.1.0
version: 0.1.1
appVersion: 4.0.13
description: NoSQL document-oriented database that stores JSON-like documents with dynamic schemas, simplifying the integration of data in content-driven applications. Sharded topology.
keywords:

View File

@@ -50,7 +50,7 @@ spec:
command: ["chown", "-R", "{{ .Values.securityContext.runAsUser }}:{{ .Values.securityContext.fsGroup }}", "{{ .Values.persistence.mountPath }}"]
securityContext:
runAsUser: 0
resources: {{ toYaml .Values.volumePermissions.resources | nindent 10 }}
resources: {{ toYaml .Values.volumePermissions.resources | nindent 12 }}
volumeMounts:
- name: datadir
mountPath: {{ .Values.persistence.mountPath }}

View File

@@ -52,7 +52,7 @@ spec:
command: ["chown", "-R", "{{ $.Values.securityContext.runAsUser }}:{{ $.Values.securityContext.fsGroup }}", "{{ $.Values.persistence.mountPath }}"]
securityContext:
runAsUser: 0
resources: {{ toYaml $.Values.volumePermissions.resources | nindent 10 }}
resources: {{ toYaml $.Values.volumePermissions.resources | nindent 12 }}
volumeMounts:
- name: datadir
mountPath: {{ $.Values.persistence.mountPath }}