1. Request quotas to ensure you have a sufficient number of resources.
2. Open the Containers sub-section and click Create container.
A new page opens. Perform the remaining steps there.
3. In the Container image block, select the image type: Public or Private. The difference between them is a password secures that private image.
nginx:latest, and go to the next step.
https://registry.mysite.com and specify registry credentials. If you have already saved them, choose Select credentials. If you do not have them, click Create credentials:
In the pop-up, enter the necessary data: Image registry name, URL, username, and password, and click Add credentials.
4. In the Port block, specify the port for connection to your container.
Note: Currently, we support only one port for the container. If you need to add additional data, create a separate container.
5. In the Container configuration block, select the MB of memory and mCPU (up to 2260 mCPU and 4096 MB) from the list. This configuration will be used for the deployed Kubernetes pod, where your container will be placed after creation.
6. 5. In the Limits of autoscaling block, enter the range for the number of nodes you want to maintain under Minimum pods and Maximum pods.
7. In the Container lifetime block, specify the number of seconds after which a pod will be deleted when there are no requests to your pod. For example, if you enter 600, the pod will be deleted in 600 seconds—equal to ten minutes.
Note: If you specify 0, the container will take approximately one minute to scale down.
8. (Optional) In the Environment variables block, create variables for your container by entering Key and Value. These variables will only be used in the environment of the created container.
9. (Optional) To protect your container endpoints from unauthorized access, enable the API Key authentication feature. Either select the API key or create a new one.
10. In the Container details block, specify the container name (this will be displayed in the customer portal) and additional information if needed.
11. On the right, click Create container. After a few minutes, the initial setup will be finished and the container will be launched.
Three statuses are available:
To change the container status to “Stopped,” go to the container settings and disable the toggle highlighted on the screenshot below:
After creating the container, click its name in the Containers tab to open its settings. Alternatively, click the three dots on the right of its row and then click Edit.
In the Overview tab, you will see the following details: container status, name of the container image, description (if you added one during creation,) and date of creation. You can’t change this information.
In the Port tab, you will see the specified port and protocol to connect to your container. This information is also unchangeable.
Click the container’s name in the Containers tab to open its settings. Alternatively, click the three dots on the right of its row and then click Edit. You can change the following configurations:
Don’t forget to click Save changes.
Open container settings and go to the Logs tab to view entities with the data about requests to your container.
Note: When you delete a container, logs are also deleted.
Logs entities are shown in the following format:
IP_Method_Endpoint_HTTP type_ Resonse code_Monitoring technology name
Open container settings, go to the Delete tab, and click Delete container. Confirm the deletion in the pop-up window that appears.
Was this article helpful?
Discover our offerings, including virtual instances starting from 3.7 euro/mo, bare metal servers, AI Infrastructure, load balancers, Managed Kubernetes, Function as a Service, and Centralized Logging solutions.