-
Notifications
You must be signed in to change notification settings - Fork 34
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #593 from G-Core/6-december-edge
- Loading branch information
Showing
3 changed files
with
149 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
--- | ||
title: caas | ||
displayName: Container as a Service | ||
published: true | ||
toc: | ||
pageTitle: Container as a Service to Run Container without Kubernetes or VM | Gcore | ||
pageDescription: A short overview of the new Gcore product—Container as a Service. | ||
--- | ||
# About Container as a Service | ||
|
||
Gcore Container as a Service (CaaS) is a cloud service that allows our customers to run containers without Kubernetes or VM management. We at Gcore take care of infrastructure maintenance and scaling on your behalf. | ||
|
||
To use CaaS, choose a supported region, pull the image of the container, and manage it via the customer portal or REST API. We have a <a href="https://gcore.com/docs/cloud/caas/manage-containers" target="_blank">separate article about creating and managing containers</a>. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,130 @@ | ||
--- | ||
title: manage-containers | ||
displayName: Manage containers | ||
published: true | ||
order: 10 | ||
toc: | ||
--1--Create: "create-a-container" | ||
--1--Statuses: "container-statuses" | ||
--1--Overview and Port tabs: "overview-and-port-tabs" | ||
--1--Change settings: "change-container-settings" | ||
--1--Logs: "logs" | ||
--1--Delete: "Delete-a-container" | ||
pageTitle: Create Containers in the Customer Portal | Gcore | ||
pageDescription: A comprehensive step-by-step guide on how to create and manage containers with the new product. | ||
--- | ||
# Manage containers | ||
|
||
## Create a container | ||
|
||
1\. <a href="https://gcore.com/docs/cloud/getting-started/request-a-quota-increase" target="_blank">Request quotas</a> to ensure you have a sufficient number of resources. | ||
|
||
2\. Open the **Containers** sub-section and click **Create container**. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-10.png" alt="Create a new container for the first time" width="80%"> | ||
|
||
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. | ||
|
||
- For public image type, enter the URL from where the image will be downloaded in the format ```https://registry.mysite.com``` and go to the next step. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-20.png" alt="Public containers" width="50%"> | ||
|
||
- For private image type, enter the URL in the format ```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**: | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-30.png" alt="Private containers" width="50%"> | ||
|
||
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. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-40.png" alt="Port for container creation" width="50%"> | ||
|
||
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. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-50.png" alt="Configuration of mCPU anf memory" width="70%"> | ||
|
||
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. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-60.png" alt="Autoscaling configuration" width="70%"> | ||
|
||
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. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-70.png" alt="Container lifetime configuration" width="70%"> | ||
|
||
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. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-80.png" alt="Variables configuration for container environment" width="70%"> | ||
|
||
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. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-90.png" alt="API key authentication for containers" width="70%"> | ||
|
||
10\. In the **Container details** block, specify the container name (this will be displayed in the customer portal) and additional information if needed. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-100.png" alt="Container details" width="70%"> | ||
|
||
11\. On the right, click **Create container**. After a few minutes, the initial setup will be finished and the container will be launched. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-110.png" alt="Create container final step" width="50%"> | ||
|
||
|
||
## Container statuses | ||
|
||
Three statuses are available: | ||
|
||
- **Started**: The initial setup was successful and the container works appropriately. | ||
- **Stopped**: You manually disabled the container in settings. | ||
- **Failed**: There were issues with the image of your container in its initial configuration and as a result, the container doesn’t work. | ||
|
||
To change the container status to “Stopped,” go to the container settings and disable the toggle highlighted on the screenshot below: | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-120.png" alt="How to stop a container" width="70%"> | ||
|
||
## Overview and Port tabs | ||
|
||
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. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-130.png" alt="Overview tab" width="70%"> | ||
|
||
In the **Port** tab, you will see the specified port and protocol to connect to your container. This information is also unchangeable. | ||
|
||
## Change container settings | ||
|
||
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: | ||
|
||
- mCPU and memory | ||
- Limits of autoscaling | ||
- API Key authentication | ||
- Variables | ||
- Lifetime | ||
|
||
Don’t forget to click **Save changes**. | ||
|
||
## Logs | ||
|
||
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: | ||
|
||
``` | ||
Container name_Date_Date | ||
IP_Method_Endpoint_HTTP type_ Resonse code_Monitoring technology name | ||
``` | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-140.png" alt="Example of the logs" width="70%"> | ||
|
||
## Delete a container | ||
|
||
Open container settings, go to the **Delete** tab, and click **Delete container**. Confirm the deletion in the pop-up window that appears. | ||
|
||
<img src="https://assets.gcore.pro/docs/cloud/caas/manage-containers/manage-containers-150.png" alt="Container deletion" width="70%"> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
--- | ||
title: metadata | ||
displayName: Container as a Service | ||
published: true | ||
order: 120 | ||
--- |