Roost - Retain control over your Cloud Cost
Setting Organisation Limits - for the Admin
Cloud Credentials - optional
Provide credentials in a secure manner
Avoids the need to setup IAM roles or share credentials
Configure Default Settings
Choose the default region, AMI type, instance type for the cluster nodes
Default the number of worker nodes and limit the maximum number of nodes allowed
Choose spot or pre-emptible instance type to save additional cost
Default the cluster auto-expire duration (in hours; user can always extend it easily)
Attach the application installation script (saves time as application is auto-installed on cluster)
Limit the maximum number of active clusters per user
User License
Decide who is allowed to spin-up clusters on the cloud
Override the maximum number of nodes for the user
Promote the user to admin role
Configure JumpServer or Bastion
Provide ip-address, user and ssh/pem key for JumpServer
Upload kubeconfig for your clusters that are accessible only via JumpServer.
View configured clusters and user sessions established via JumpServer.
Manage/kill user sessions
Â
Â
Â