[New cluster] Kitware #3929
[New cluster] Kitware #3929
Conversation
|
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deploymentsNo production hub upgrades will be triggered |
| ````{warning} | ||
| If you are deploying the support chart on an AWS cluster, you **must** enable the `cluster-autoscaler` sub-chart, otherwise the node groups will not automatically scale. | ||
| Include the following in your `support.values.yaml` file: | ||
|
|
||
| ```yaml | ||
| cluster-autoscaler: | ||
| enabled: true | ||
| autoDiscovery: | ||
| clusterName: <cluster-name> | ||
| awsRegion: <aws-region> | ||
| ``` | ||
| ```` |
There was a problem hiding this comment.
@consideRatio, apparently it was still documented, I might have missed it when deploying dandi. Anyway, I've removed it now that we autogenerate it via the deployer.
|
Thank you @consideRatio 🚀
Wasn't sure what to do about this, but tried not to assume and followed the docs as close as possible as an experiment. As long as we can add it later, if it's explicitly required, I think it's fine. We can also add it las a general good practice in the docs as you said. |
|
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/8643319425 |
Ref #3906
Also updates some things in the docs while walking through them.