Skip to content

Commit

Permalink
Merge pull request #6682 from dokku/josegonzalez-patch-1
Browse files Browse the repository at this point in the history
Fix reference to formation key in autoscaling example
  • Loading branch information
josegonzalez committed Mar 7, 2024
2 parents daf86d0 + 628b68c commit 202d4ed
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/deployment/schedulers/k3s.md
Original file line number Diff line number Diff line change
Expand Up @@ -365,7 +365,7 @@ dokku scheduler-k3s:labels:set node-js-app label.key --resource-type deployment
Autoscaling in k3s is managed by [Keda](https://keda.sh/), which integrates with a variety of external metric providers to allow for autoscaling application workloads.

To enable autoscaling, use the `app.json` `formations.$PROCESS_TYPE.autoscaling` key to manage rules. In addition to the existing configuration used for process management, each process type in the `formations.$PROCESS_TYPE.autoscaling` key can have the following keys:
To enable autoscaling, use the `app.json` `formation.$PROCESS_TYPE.autoscaling` key to manage rules. In addition to the existing configuration used for process management, each process type in the `formation.$PROCESS_TYPE.autoscaling` key can have the following keys:

- `min_quantity`: The minimum number of instances the application can run. If not specified, the `quantity` specified for the app is used.
- `max_quantity`: The maximum number of instances the application can run. If not specified, the higher value of `quantity` and the `min_quantity` is used.
Expand All @@ -377,7 +377,7 @@ Autoscaling triggers are passed as is to Keda, and should match the configuratio

```json
{
"formations": {
"formation": {
"web": {
"autoscaling": {
"min_quantity": 1,
Expand Down

0 comments on commit 202d4ed

Please sign in to comment.