Select one if you have already created an Application in Cuemby Cloud Platform or click on “Create” to create a new Application.
First, name the Application you are going to create. You can use lowercase letters, numbers and dash, but no spaces and special characters are allowed.
Registry guide coming soon!
Then, select a Git code repository provider if you already integrated with one or set up a new integration. The Platform currently offers integration with GitHub, Bitbucket and GitLab.
If you have not integrated your repository with the platform and are creating a new one, name the integration you are going to create. You can use lowercase, numbers, and dash, but no spaces and special symbols are allowed. Then, choose a Git Provider that you are going to integrate with.
You might need to go through an extra step to authorize the platform to integrate with GitHub, GitLab or Bitbucket if you didn't register with the repository service provider.
Once you are integrated with the Git Provider, a modal will appear, and you need to select a workspace. Your personal workspace is selected by default.
You can also choose from the dropdown menu, which is the list of workspaces that you belong to.
Next, select an instant type. You can select from Extra small, small, medium. Large or Extra Large. They are the types of instances where your Application will be running. The instance type depends on the size of your Application and how much resource that the Application consumes. The types are:
Extra small – CPU 100m, RAM 128 Mi
Small – CPU 200m, RAM 256Mi
Medium – CPU 600m, RAM 384Mi
Large – CPU 300m, RAM 768Mi
Extra Large – CPU 1000m, RAM 1024Mi
Next, choose the traffic type of the Application. If your Application is open to the public and interacts with traffic that is outside your project, please select External. If your application is to service other Applications in the same project internally, you can select internal. It is important to note that when you create a Runtime, the platform automatically generates a CloudFlare Origin Certificate Authority (Origin CA).
By selecting the option “External,” Cuemby Cloud Platform provides more robust security to your infrastructure. Ingress certificates are automatically renewed, eliminating the need for manual updates and the worry of missing expiration.
By selecting the option “Internal,” Cuemby Cloud Platform generates an endpoint to consume at the cluster level, which is identified through a DNS.
In the next section, add environment variables for your application. If you have sensitive information, you are able to encrypt the information by clicking on the Encrypt lock icon. You can add as many environment variables as you would like by clicking on the “+” icon.
Let's add a scaling strategy. The fields in the section are pre-filled. If you are not sure, you can use the pre-defined values. However, if you are planning on running a robust application, you may need to make changes.
Cool down period is how many seconds you want to wait before scaling down when you no longer need replicas. The default is 30 seconds.
Polling Interval is how often the platform should be checking if the application is complied with the scaling strategy. The default is 30 seconds.
Minimum Replica is the minimum number of replicas you want to run when your application does not need to scale. The default is 1.
Lastly, Maximum Replica is the maximum number of replicas you want to run when your application needs to scale. The default is 2.
After defining the scaling strategies, click on “Next.”