Skip to content

Commit 285f3be

Browse files
Tahiya Chowdhuryjwilliams-mongo
authored andcommitted
(DOCSP-4987): Add troubleshooting entry for replacing configmaps
1 parent 517cefb commit 285f3be

File tree

1 file changed

+15
-6
lines changed

1 file changed

+15
-6
lines changed

source/reference/troubleshooting.txt

Lines changed: 15 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -306,17 +306,26 @@ those pods.
306306

307307
.. _replace-config-file:
308308

309-
Force Replace a Config File to Reflect Changes
310-
----------------------------------------------
309+
Replace a Configuration File to Reflect Changes
310+
-----------------------------------------------
311311

312-
Invoke the following command to replace a config file:
312+
To modify or redeploy an already-deployed configuration file, invoke the following command:
313313

314314
.. code-block:: shell
315315

316-
kubectl replace -f <configfilename>.yaml
316+
kubectl replace -f <filename>.yaml
317317

318-
This deletes and re-creates the resource. It is useful in cases where you need to update resource fields that cannot be updated once
319-
initialized, or you just want to propagate changes made in the configMap to other config files.
318+
Use this command to propogate any changes made in the configMap to a config file.
319+
320+
321+
To delete and re-create a resource, add the *--force* flag:
322+
323+
.. code-block:: shell
324+
325+
kubectl replace --force -f <filename>.yaml
326+
327+
This command is useful in cases where you need to update resource files that cannot be updated once
328+
initialized or want to make an immediate recursive change.
320329

321330
.. _remove-k8s-resource:
322331

0 commit comments

Comments
 (0)