Skip to content

Commit f101cd0

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

File tree

1 file changed

+7
-15
lines changed

1 file changed

+7
-15
lines changed

source/reference/troubleshooting.txt

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

307307
.. _replace-config-file:
308308

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

312-
To modify or redeploy an already-deployed configuration file, invoke the following command:
312+
If you are unable to modify or redeploy an already-deployed configMap file using the *kubectl apply* command, invoke the following
313+
instead:
313314

314315
.. code-block:: shell
315316

316-
kubectl replace -f <filename>.yaml
317+
kubectl replace -f <my-config-map>.yaml
317318

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.
319+
This will delete and re-create a resource. This command is useful in cases where you need to update resource files that cannot be updated
320+
once initialized or want to make an immediate recursive change.
329321

330322
.. _remove-k8s-resource:
331323

0 commit comments

Comments
 (0)