Skip to content

Commit

Permalink
docs: Reword AMI tasks to options (aws#5815)
Browse files Browse the repository at this point in the history
Co-authored-by: Jonathan Innis <[email protected]>
  • Loading branch information
2 people authored and engedaam committed Mar 27, 2024
1 parent 5acb150 commit ab6c07d
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion website/content/en/v0.32/tasks/managing-amis.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ Extending those values causes longer times without disruption.
Settings for budgets in the above example include the following:

* **Percentage of nodes**: From the first `nodes` setting, only `15%` of the NodePool’s nodes can be disrupted at a time.
* **Number of nodes**: The second `nodes` setting limits the number of nodes that can be disrupted at a time to `3`.
* **Number of nodes**: The second `nodes` setting limits the number of nodes that can be disrupted at a time to `5`.
* **Schedule**: The third `nodes` setting uses schedule to say that zero disruptions (`0`) are allowed starting at 7am on Saturday and Sunday and continues for 12 hours.
The format of the schedule follows the `crontab` format for identifying dates and times.
See the [crontab](https://man7.org/linux/man-pages/man5/crontab.5.html) page for information on the supported values for these fields.
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/v0.33/tasks/managing-amis.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ Extending those values causes longer times without disruption.
Settings for budgets in the above example include the following:

* **Percentage of nodes**: From the first `nodes` setting, only `15%` of the NodePool’s nodes can be disrupted at a time.
* **Number of nodes**: The second `nodes` setting limits the number of nodes that can be disrupted at a time to `3`.
* **Number of nodes**: The second `nodes` setting limits the number of nodes that can be disrupted at a time to `5`.
* **Schedule**: The third `nodes` setting uses schedule to say that zero disruptions (`0`) are allowed starting at 7am on Saturday and Sunday and continues for 12 hours.
The format of the schedule follows the `crontab` format for identifying dates and times.
See the [crontab](https://man7.org/linux/man-pages/man5/crontab.5.html) page for information on the supported values for these fields.
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/v0.34/tasks/managing-amis.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ Extending those values causes longer times without disruption.
Settings for budgets in the above example include the following:

* **Percentage of nodes**: From the first `nodes` setting, only `15%` of the NodePool’s nodes can be disrupted at a time.
* **Number of nodes**: The second `nodes` setting limits the number of nodes that can be disrupted at a time to `3`.
* **Number of nodes**: The second `nodes` setting limits the number of nodes that can be disrupted at a time to `5`.
* **Schedule**: The third `nodes` setting uses schedule to say that zero disruptions (`0`) are allowed starting at 7am on Saturday and Sunday and continues for 12 hours.
The format of the schedule follows the `crontab` format for identifying dates and times.
See the [crontab](https://man7.org/linux/man-pages/man5/crontab.5.html) page for information on the supported values for these fields.
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/v0.35/tasks/managing-amis.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ Extending those values causes longer times without disruption.
Settings for budgets in the above example include the following:

* **Percentage of nodes**: From the first `nodes` setting, only `15%` of the NodePool’s nodes can be disrupted at a time.
* **Number of nodes**: The second `nodes` setting limits the number of nodes that can be disrupted at a time to `3`.
* **Number of nodes**: The second `nodes` setting limits the number of nodes that can be disrupted at a time to `5`.
* **Schedule**: The third `nodes` setting uses schedule to say that zero disruptions (`0`) are allowed starting at 7am on Saturday and Sunday and continues for 12 hours.
The format of the schedule follows the `crontab` format for identifying dates and times.
See the [crontab](https://man7.org/linux/man-pages/man5/crontab.5.html) page for information on the supported values for these fields.
Expand Down

0 comments on commit ab6c07d

Please sign in to comment.