Expand your Orion cluster

Cloud

If you are using a cloud deployment, we recommend you install an Autoscaler for your cluster. With an autoscaler, whenever you request a workstation, Kubernetes will check for available compute resources.

If your current cluster cannot run the workstation you had requested, it will automatically bring online another node. Once you configure your autoscaler, it will also bring down any unused nodes, making sure you are not being charged for them and are utilizing only the necessary resources.

For AWS deployments, we highly recommend:

• Karpenter
• Cluster Autoscaler

Offline/air-gapped considerations

For offline installations, make sure that:

• the juno-fx/ansible-ee:latest image can be pulled from your nodes via the configuration in /etc/rancher/k3s/registries.yaml
• this configuration is set up automatically when using our install helper script found in the Quick Start Guide
• if you adjust it, please make sure to do so across all your control plane nodes
• when expanding the cluster, the file will be copied from your control plane node to any newly added nodes
  • when you have multiple nodes, this will be performed on one of them. That is why it's important this file is consistent across the board.

On-Premise (k3s)

You can expand your cluster in genesis via the network page. Read more about node provisioning here