Getting started
Guides and examples
Reference documentation
Background concepts
Frequently Asked Questions
Integrations
Preparing Your Account
Create an account
You'll need to create an account to get started with Release.
Release supports the following source control systems: GitHub, GitBucket, GitLab. Release will integrate with your source control system and create your account.
You may want to log in to Release and turn off automatic PR creation until you are ready to use Release. This will prevent failed builds and deploys from cluttering your view and worrying developers working on the codebase.
Integrate with your cloud provider
Release will need to integrate with your cloud provider to provision and manage your new environment. Release currently supports Amazon Web Services, Amazon Web Services GovCloud, and Google Cloud Platform for cloud integration.
Refer to the appropriate guide for connecting your cloud provider to Release:
Create a cluster
There are only three major decisions you'll need to make when creating a cluster: choosing DNS names, number and type of nodes, and whether to specify network addresses.
DNS names
Release will build your ephemeral environments under a subdomain that you control. We recommend that you choose a domain that is short (so it’s easier to type) and clearly identifies that your environments are ephemeral.
We don't advise that you run ephemeral and production environments together.
You can choose use the Release subdomain along with your corporate domain name, for example:
1
release.example.com
Copied!
Your environments could then be named as follows:
1
serviceA-envA.release.example.com
2
serviceB-envA.release.example.com
3
serviceA-envB.release.example.com
4
serviceB-envB.release.example.com
Copied!
Alternatively, you could use a development domain that is separate from your corporate domain name, for example:
1
release.example.dev
2
release.example-dev.io
Copied!
Node type and number
Release uses Kubernetes clusters under the hood. You'll need to 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 Release, you can seamlessly upgrade, increase, decrease, or resize your cluster later without any interruption.
Network addresses (CIDR blocks)
Release environments run inside your cloud provider account, and they might need to be connected to existing services and applications that run there. However, it is not essential to connect the environments, and you may want to keep the Release environments completely separate from your other running applications.
In order to keep Release environments from interfering with existing applications, 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 tell us what it is when we create the cluster and we will build a Virtual Private Cloud with the unique CIDR block you provide. However, if you do not know what block to use, you can use the defaults.
See also
Last modified 1mo ago