Roost - Retain control over your Cloud Cost

Owned by Harish Agrawal
Feb 28, 2022
1 min read

Setting Organisation Limits - for the Admin

Cloud Credentials - optional

  1. Provide credentials in a secure manner

  2. Avoids the need to setup IAM roles or share credentials

Configure Default Settings

  1. Choose the default region, AMI type, instance type for the cluster nodes

  2. Default the number of worker nodes and limit the maximum number of nodes allowed

  3. Choose spot or pre-emptible instance type to save additional cost

  4. Default the cluster auto-expire duration (in hours; user can always extend it easily)

  5. Attach the application installation script (saves time as application is auto-installed on cluster)

  6. Limit the maximum number of active clusters per user

User License

  1. Decide who is allowed to spin-up clusters on the cloud

  2. Override the maximum number of nodes for the user

  3. Promote the user to admin role

Configure JumpServer or Bastion

  1. Provide ip-address, user and ssh/pem key for JumpServer

  2. Upload kubeconfig for your clusters that are accessible only via JumpServer.

  3. View configured clusters and user sessions established via JumpServer.

  4. Manage/kill user sessions