Kubernetes/ConfigMap and Secrets - Revision history

Pio2pio: /* ConfigMap mounted as a volume */

2021-01-11T10:22:42Z

ConfigMap mounted as a volume

← Older revision		Revision as of 12:22, 11 January 2021
Line 36:		Line 36:

	= ConfigMap mounted as a volume =		= ConfigMap mounted as a volume =
			ConfigMap mounted as <code>subPath</code> it won’t update until the pod restarts. The files are not-symlnks:
			<source lang=bash>
			$ kubectl -n production exec go-conf-example-6b4cb86569-22vqv -- ls -lha /app/configfiles
			total 20K
			drwxr-xr-x 1 root root 4.0K Mar 3 19:34 .
			drwxr-xr-x 1 app app 4.0K Mar 3 19:34 ..
			-rw-r--r-- 1 root root 42 Mar 3 19:34 config.json
			-rw-r--r-- 1 root root 47 Mar 3 19:34 database.yml
			</source>


			Mount it as a <code>directory</code> (without subPath), your container will get a continuously up-to-date config file. Notice in this case the files are actually the <code>sym-links</code>:
			<source lang=bash>
			$ kubectl -n production exec go-conf-example-67c768c6fc-ccpwl -- ls -lha /app/configfiles
			total 12K
			drwxrwxrwx 3 root root 4.0K Mar 3 19:40 .
			drwxr-xr-x 1 app app 4.0K Mar 3 19:34 ..
			drwxr-xr-x 2 root root 4.0K Mar 3 19:40 ..2020_03_03_16_40_36.675612011
			lrwxrwxrwx 1 root root 31 Mar 3 19:40 ..data -> ..2020_03_03_16_40_36.675612011
			lrwxrwxrwx 1 root root 18 Mar 3 19:40 config.json -> ..data/config.json
			lrwxrwxrwx 1 root root 19 Mar 3 19:40 database.yml -> ..data/database.yml
			</source>

	= ConfigMap and Secrets mounted as a volume and $ENV =		= ConfigMap and Secrets mounted as a volume and $ENV =

Pio2pio: /* ConfigMap changes behaviours */

2021-01-11T09:41:07Z

ConfigMap changes behaviours

← Older revision		Revision as of 11:41, 11 January 2021
Line 33:		Line 33:
	4. <code>ConfigMap</code> mounted as a directory has been modified.		4. <code>ConfigMap</code> mounted as a directory has been modified.
	* The effect: the config file in the pod will be updated automatically, without restarting/rescheduling the pod.		* The effect: the config file in the pod will be updated automatically, without restarting/rescheduling the pod.


			= ConfigMap mounted as a volume =

	= ConfigMap and Secrets mounted as a volume and $ENV =		= ConfigMap and Secrets mounted as a volume and $ENV =

Pio2pio: /* ConfigMap and Secrets mounted as a volume and $ENV */

2021-01-11T09:09:31Z

ConfigMap and Secrets mounted as a volume and $ENV

@@ Line 15: / Line 15: @@
    anotherKey: myValue2
 </syntaxhighlightjs>
 = ConfigMap and Secrets mounted as a volume and $ENV =

Pio2pio: /* References */

2020-11-14T16:49:14Z

References

@@ Line 309: / Line 309: @@
 No Base64 updade string
 </source>
 =References=
 *[https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/ configure-pod-configmap]
 *[https://kubernetes.io/docs/concepts/configuration/secret/ Secretes]

Pio2pio: /* References */

2020-07-27T12:49:48Z

References

@@ Line 285: / Line 285: @@
 |}
 =References=
 *[https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/ configure-pod-configmap]
 *[https://kubernetes.io/docs/concepts/configuration/secret/ Secretes]

Pio2pio: /* configMap mounted as a volume with subPath */

2020-04-06T19:11:51Z

configMap mounted as a volume with subPath

← Older revision		Revision as of 21:11, 6 April 2020
Line 125:		Line 125:
	- "7200"		- "7200"
	volumeMounts:		volumeMounts:
	- name: ~~netmount~~-volume		- name: configmap-volume
	mountPath: /etc/~~address~~		mountPath: /etc/file1
	subPath: file1 # lookup on CM data, the filename is a data.address key here 'address'		subPath: file1 # lookup on CM data, the filename is \
	~~- name: netmount-volume~~		- name: configmap-volume # a data.address key here 'address'
	mountPath: /~~file.txt~~		mountPath: /file2
	subPath: file2 ~~# lookup on CM data, the filename is a data.address key here 'address'~~		subPath: file2
	- name: ~~netmount~~-volume		- name: configmap-volume
	mountPath: /etc/~~motd~~		mountPath: /etc/file2
	subPath: file2		subPath: file2
	volumes:		volumes:
Line 140:		Line 140:
	</syntaxhighlightjs>		</syntaxhighlightjs>
	\|}		\|}

			{{Note\|<code>SubPaths</code> are not automatically updated when a ConfigMap is modified. Changes to a ConfigMap will need to be a new deployment which would result in the pods being recreated with the updated ConfigMap content.\|info}}

Pio2pio: /* ConfigMap and Secrets mounted as a volume and $ENV */

2020-04-06T19:04:32Z

ConfigMap and Secrets mounted as a volume and $ENV

← Older revision		Revision as of 21:04, 6 April 2020
Line 88:		Line 88:
	kubectl logs configmap-pod #Get the logs from the pod displaying the value		kubectl logs configmap-pod #Get the logs from the pod displaying the value
	</source>		</source>

			= configMap mounted as a volume with <tt>subPath</tt> =
			{\| class="wikitable"
			\|+ ConfigMap
			\|- style="vertical-align:top;"
			! Pod manifest
			! ConfigMap
			\|- style="vertical-align:top;"
			\| <syntaxhighlightjs lang=yaml>
			# cat cm-configmap.yaml
			apiVersion: v1
			kind: ConfigMap
			metadata:
			name: cm-configmap
			data:
			file1: \|
			Line 1 in file1
			file2: \|
			Line 1 in file2
			Line 2
			</syntaxhighlightjs>
			\| <syntaxhighlightjs lang=yaml>
			# cat pod-configMap-volume.yaml
			---
			apiVersion: v1
			kind: Pod
			metadata:
			name: centos-1
			namespace: pipaw
			spec:
			containers:
			- name: centos
			image: centos:7.6.1810
			command:
			- sleep
			- "7200"
			volumeMounts:
			- name: netmount-volume
			mountPath: /etc/address
			subPath: file1 # lookup on CM data, the filename is a data.address key here 'address'
			- name: netmount-volume
			mountPath: /file.txt
			subPath: file2 # lookup on CM data, the filename is a data.address key here 'address'
			- name: netmount-volume
			mountPath: /etc/motd
			subPath: file2
			volumes:
			- name: configmap-volume
			configMap:
			name: cm-configmap
			</syntaxhighlightjs>
			\|}

Pio2pio: /* ConfigMap and Secrets mounted as a volume and $ENV */

2020-04-06T18:44:23Z

ConfigMap and Secrets mounted as a volume and $ENV

← Older revision		Revision as of 20:44, 6 April 2020
Line 20:		Line 20:
	\|+ ConfigMap		\|+ ConfigMap
	\|- style="vertical-align:top;"		\|- style="vertical-align:top;"
	! ~~As a~~ environment		! ConfigMap value read into environment var
	! ~~Mounted~~ volume		! ConfigMap mounted as a volume
	! Secrets mounted volume		! Secrets mounted as a volume
	\|- style="vertical-align:top;"		\|- style="vertical-align:top;"
	\| <syntaxhighlightjs lang=yaml>		\| <syntaxhighlightjs lang=yaml>
			# cat pod-configMap-env.yaml
	apiVersion: v1		apiVersion: v1
	kind: Pod		kind: Pod
	metadata:		metadata:
	name: ~~kube~~-~~configmap~~		name: pod-configMap-env
	spec:		spec:
	containers:		containers:
Line 41:		Line 42:
	key: value1		key: value1
	</syntaxhighlightjs>		</syntaxhighlightjs>
	\| <syntaxhighlightjs lang=yaml>apiVersion: v1		\| <syntaxhighlightjs lang=yaml>
			# cat pod-configMap-volume.yaml
			apiVersion: v1
	kind: Pod		kind: Pod
	metadata:		metadata:
	name: ~~configmap~~-volume~~-kube~~		name: pod-configMap-volume
	spec:		spec:
	containers:		containers:
Line 59:		Line 62:
	</syntaxhighlightjs>		</syntaxhighlightjs>
	\| <syntaxhighlightjs lang=yaml>		\| <syntaxhighlightjs lang=yaml>
			# cat pod-secret-volume.yaml
	apiVersion: v1		apiVersion: v1
	kind: Pod		kind: Pod
	metadata:		metadata:
	name: ~~kube~~-secret-volume~~-pod~~		name: pod-secret-volume
	spec:		spec:
	containers:		containers:
Line 81:		Line 85:
	Deploy configMap		Deploy configMap
	<source lang=bash>		<source lang=bash>
	kubectl apply -f ~~configmap~~-pod.yaml		kubectl apply -f pod-configMap-env.yaml # pod-configMap-volume.yaml \| pod-secret-volume.yaml
	kubectl logs configmap-pod #Get the logs from the pod displaying the value		kubectl logs configmap-pod #Get the logs from the pod displaying the value
	</source>		</source>

Pio2pio at 18:34, 6 April 2020

2020-04-06T18:34:56Z

← Older revision		Revision as of 20:34, 6 April 2020
Line 1:		Line 1:
			= ConfigMap =
	ConfigMap object allows to manage application's configuration using Kubernetes primitives. YAML below:		ConfigMap object allows to manage application's configuration using Kubernetes primitives. YAML below:
	<source lang=bash>		<source lang=bash>
Line 15:		Line 16:
	</syntaxhighlightjs>		</syntaxhighlightjs>

			= ConfigMap and Secrets mounted as a volume and $ENV =
	{\| class="wikitable"		{\| class="wikitable"
	\|+ ConfigMap		\|+ ConfigMap

Pio2pio at 20:24, 20 October 2019

2019-10-20T20:24:00Z

← Older revision		Revision as of 22:24, 20 October 2019
Line 18:		Line 18:
	{\| class="wikitable"		{\| class="wikitable"
	\|+ ConfigMap		\|+ ConfigMap
	\|-		\|- style="vertical-align:top;"
	! As a environment		! As a environment
	! Mounted volume		! Mounted volume
	! Secrets mounted volume		! Secrets mounted volume
	\|-		\|- style="vertical-align:top;"
	\| <syntaxhighlightjs lang=yaml>		\| <syntaxhighlightjs lang=yaml>
	apiVersion: v1		apiVersion: v1
Line 90:		Line 90:
	kubectl exec configmaps-volume-kube -- cat /etc/config/key1		kubectl exec configmaps-volume-kube -- cat /etc/config/key1
	</source>		</source>


	= Secrets =		= Secrets =
Line 153:		Line 152:
	{\| class="wikitable"		{\| class="wikitable"
	\|+ ConfigMap		\|+ ConfigMap
	\|-		\|- style="vertical-align:top;"
	! As a environment		! As a environment
	! Secrets mounted volume		! Secrets mounted volume
	\|-		\|- style="vertical-align:top;"
	\| <syntaxhighlightjs lang=yaml>		\| <syntaxhighlightjs lang=yaml>
	apiVersion: v1		apiVersion: v1