Kubectl patch: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
=Usage Examples= | =Usage Examples= | ||
==Delete a Field== | ==<span id='Delete_a_Field'></span>Delete a Field with a JSON Patch== | ||
Unbind a PVC from a PV by deleting the PV's <code>claimRef</code>: | Unbind a PVC from a PV by deleting the PV's <code>claimRef</code>: | ||
<syntaxhighlight lang='bash'> | <syntaxhighlight lang='bash'> | ||
kubectl patch pv my-pv --type=json -p='[{"op": "remove", "path": "/spec/claimRef"}]' | kubectl patch pv my-pv --type=json -p='[{"op": "remove", "path": "/spec/claimRef"}]' | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Revision as of 17:30, 29 July 2021
External
Internal
Overview
kubectl patch supports the following modes: strategic merge patch ("strategic"), JSON merge patch ("merge") and JSON patch ("json").
Caveats
⚠️There are situations when the patch apparently succeeds, the kubectl patch command exits with 0 and if the resource is queried immediately, the patch seems to be applied, but when the resource is queried a while later (15 secs), it becomes apparent that the "patch" did not take. This happened while trying to unbind a PV from the PVC while the PVC is still active.
Usage Examples
Delete a Field with a JSON Patch
Unbind a PVC from a PV by deleting the PV's claimRef:
kubectl patch pv my-pv --type=json -p='[{"op": "remove", "path": "/spec/claimRef"}]'