Create a cluster
To create a cluster, navigate to your account settings and then to the "Clusters" tab. Press "Create new cluster" and select the existing cloud integration that you want to create the cluster in. Choose a region, an IP range, the Kubernetes version, and domain to use with this cluster. If you want, change the cluster name, or leave the autogenerated one.
Click Clusters in the sidebar, then click the green Create New Cluster button in the "Clusters" section. Note that only account owners may create new clusters.
This will spin up a new Kubernetes cluster in your cloud provider (for example, using EKS if you've integrated with AWS.) Note that this will create compute resources in your cloud provider account which you will be billed for.
If you're not sure which IP range to use, you can use choose any one from the drop down.
ReleaseHub environments run inside your cloud provider account, and these might need to connect to existing services and applications that run there. Conversely, you might need to fully isolate your ReleaseHub environments from existing services.
In order to keep ReleaseHub environments from interfering with existing applications, by default we select a network address or CIDR block that is distinct from the other network addresses you use in your enterprise. If you know which CIDR block to use, go ahead and select that. ReleaseHub will build a Virtual Private Cloud (VPC) with the unique CIDR block you provide.
After creating your cluster, you'll automatically have a default node group. If you want to reduce costs (for example, if you're still experimenting with ReleaseHub), you can set the minimum, maximum, and desired node size to 1 (or even 0).
From the cluster settings page, you can also upgrade the cluster, set it as default, or add more node groups.
Note that you can set a minimum and maximum number of nodes, and the type of node that your cloud provider will use to host the workloads.
The size of cluster you need will depend on your application stack, use case, and team size. Unless you know for sure how many environments you will be running at once and what each workload will be, the best option is to choose the defaults (min: 3, max: 10, type: 16GiB/4 CPUs).
With ReleaseHub, you can seamlessly upgrade, increase, decrease, or resize your cluster later without any interruption, so you can always change this later if you need more compute power or want to reduce your cloud bill.