Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: minor readability on migration #3427

Merged
merged 1 commit into from
Mar 8, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/migrating.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,10 +55,11 @@ Instead of removing Deployment you can scale it down to zero and reference it fr
1. Create a Rollout resource.
1. Reference an existing Deployment using `workloadRef` field.
1. In the `workloadRef` field set the `scaleDown` attribute, which specifies how the Deployment should be scaled down. There are three options available:
* "never": the Deployment is not scaled down
* "onsuccess": the Deployment is scaled down after the Rollout becomes healthy
* "progressively": as the Rollout is scaled up the Deployment is scaled down.
Alternatively, manually scale down an existing Deployment by changing replicas field of an existing Deployment to zero.
* `never`: the Deployment is not scaled down
* `onsuccess`: the Deployment is scaled down after the Rollout becomes healthy
* `progressively`: as the Rollout is scaled up the Deployment is scaled down.

Alternatively, manually scale down an existing Deployment by changing replicas field of an existing Deployment to zero.
1. To perform an update, the change should be made to the Pod template field of the Deployment.

Below is an example of a Rollout resource referencing a Deployment.
Expand Down