Creating Containerized Applications with the Easy Deploy Feature

Easy Deploy - Overview

The Easy Deploy feature allows you to pull images directly from Scaleway Container Registry, instantly deploying containerized applications in your Kubernetes Kapsule cluster.

With only the basic options to set, you can use Kubernetes Kapsule without managing your .yaml manifests.


Deploying a Container

To deploy a container from an image stored within Container Registry, you must be logged in to the Scaleway Console.

1 . Access the Kapsule dashboard.

2 . Click on the name of the cluster you wish to deploy your image on. The Cluster Information tab displays.

3 . Click on the Easy Deploy tab.

4 . Then, on Deploy a Container.

5 . Enter a name for your container as well as the Kubernetes namespace on which the deployment will run. A default namespace is attributed if the value is not specified.

6 . Select the namespace you would like to deploy from the Container Registry. Specify Container and Tag.

Note: Your container needs to be public in order to be selected and deployed.

You can configure the deployment of your clusters in two ways: Deployments or Cron Jobs.

A Deployment represents a set of identical Pods with no individual identities, managed by a deployment controller. The deployment controller runs multiple replicas of an application as specified in a ReplicaSet. In case any pods may fail or become unresponsive, the deployment controller replaces them until the actual state equals the desired state. By using a Deployment Kubernetes object, you do not need to manage your Pods nor your ReplicaSet.

You can set-up a Load Balancer for your container, create several replicas and add environment variables, such as database host/credentials, for example.

CronJobs in Kubernetes work like traditional cron jobs in Linux. They can be used to run tasks at a specific time or interval and may be useful for Jobs such as backups or cleanup tasks. You can edit your Deployments and CronJobs settings, but cannot modify the type of deployment nor the Container to deploy. If you need to do so, you will need to delete the existing deployment and create a new one accordingly.

For cronjobs an instruction schedule must be defined. Each Cron instruction is scheduled using the following syntax:

Minute (mm): 0 - 59
Hour (hh): 0 - 23
Day of the Month (dd): 1 - 31
Month (MMM): 1 - 12
Day of the Week (DDD): 0 - 6 (Sunday to Saturday, 7 is also Sunday on some systems)

Each instruction can also be:

*: at each unit (1, 2, 3, 4...)
5,8: at unit 5 and 8
2-5: at unit 2 to 5
*/3: every 3 unit (0, 3, 6, 9...)
10-20/3: every 3 units, between the tenth and the twentieth (10, 13, 16, 19)
Example: 45 23 * * 6
This example executes program at 23:45 (11:45 PM) every Saturday.

You must also include a path to your script in the Command box and set-up environment variables.

7 . Select a deployment type and fill out the prompted information according to your choice.

A summary of your choices is available.

8 . Click on Deploy a Container to proceed. A list of your containers displays.

Editing and Deleting Containers

To edit the configuration of a container, click on the next to its name and then on Edit.

A pop-up appears with the configuration options.

Note: The container Type cannot be modified. If you wish to use a different type, a new container must be created.

After including your modifications, click on Update Container to conclude.

If you would like to delete a container, click on the button next to the container name and then on Delete.

A pop-up appears to request confirmation. If you are sure to delete the deployment, click on Delete Deployment

Discover the Cloud That Makes Sense