[DOC] Remove backup command from CO upgrade procedure #2766
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Daniel Laing dlaing@redhat.com
Type of change
Description
Edits the procedure for Upgrading the Cluster Operator.
Step one contains a command for backing up your existing Cluster Operator resources before starting the upgrade:
kubectl get all -l app=strimzi -o yaml > strimzi-backup.yaml
This command is misleading: it doesn't work everywhere because of missing labels, it doesn't back up everything, and doesn't make it any easier to extract the changes pre-upgrade. Therefore, I've replaced this with a general step advising users to take note of any configuration changes made to their existing CO resources.
I've also made some other changes to improve the readability of the procedure.
Checklist
Please go through this checklist and make sure all applicable tasks have been done
./design