Configuring Team Cluster
It is recommended to start a Remote Roost Cluster and associate it as a team cluster.
There are multiple benefits of Remote Roost Cluster.
Benefits:
Define a cluster on cloud vendor of your choice (AWS or GCP)
Build either a heterogenous or homogenous cluster
Scale up/down with a single click
Deploy third-party tools like Clair scan, Falco, Jenkins-X with ease (Roost integration is available)
Custom Docker daemon and docker registry readily available along with cluster
Roost Desktop provides an integrated access to the cluster nodes
Roost Desktop provides an exclusive lock for shared cluster so that team members do not step on each other
Activity against the team cluster is all audit-trailed and visible via team dashboard
Steps
Start a remote cluster using Roost.ai “Partner Dashboard” or Roost Desktop, “Cluster Management View”
Once cluster goes to running (typically in under 10 minutes), go to Collaboration View “My Teams”
Using the Admin View on the teams page, you can associate any running cluster as the team cluster
Choose the remote cluster, identifiable by the cluster alias
Next Steps towards automated validation and certification
Enabling Service Fitness for Team Cluster
Configuring the team cluster for automated GitOps
Configuring the team cluster for JenkinsX