Skip to content

Commit 1c8da0d

Browse files
SamyOubouazizSamyOubouaziz
committed
docs(srv): update
1 parent 62bb55e commit 1c8da0d

File tree

2 files changed

+78
-22
lines changed

2 files changed

+78
-22
lines changed

‎pages/serverless-containers/how-to/deploy-container.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ You can deploy a container from the [Scaleway Container Registry](/container-reg
4444
- **Request concurrency**: your container automatically scales up/down within the minimum and maximum values entered based on the number of concurrent requests received on each active instance of your container.
4545
- **CPU percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the CPU load.
4646
- **RAM percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the RAM used.
47-
6. In the **Advanced options** section set the following:
47+
6. In the **Advanced options** section, set the following:
4848
<Tabs>
4949
<TabsTab label="Data">
5050
- Declare [environment variables](/serverless-containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair.
@@ -107,7 +107,7 @@ Private external container registries are currently not supported.
107107
- **Request concurrency**: your container automatically scales up/down within the minimum and maximum values entered based on the number of concurrent requests received on each active instance of your container.
108108
- **CPU percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the CPU load.
109109
- **RAM percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the RAM used.
110-
6. In the **Advanced options** section set the following:
110+
6. In the **Advanced options** section, set the following:
111111
<Tabs>
112112
<TabsTab label="Data">
113113
- Declare [environment variables](/serverless-containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair.

‎pages/serverless-containers/how-to/manage-a-container.mdx‎

Lines changed: 76 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -28,34 +28,90 @@ This page shows you how to manage a container, should you need to verify or edit
2828

2929
1. Click **Containers** in the **Serverless** section of the side menu. The Containers page displays.
3030
2. Click the relevant containers namespace.
31-
3. Click the name of the container you want to manage.
32-
4. Check or edit any of the following information as required, on the **Deployment** tab:
31+
3. Click the name of the container you want to manage, then select the **Settings** tab.
32+
4. In the **Container image** section:
3333
- Select the **Scaleway** Container Registry.
3434
- Choose an **image** from your Container Registry. Select the required Container Registry namespace from the drop-down list, and then select the container and tag.
35-
- Choose the **Port** your container is listening on. We recommend configuring your container to listen on the **PORT** environment variable.
36-
- Choose the **resources** to be allocated to your container at runtime. These define the performance characteristics of your container.
37-
- Set your **scaling** preferences, or leave them at default values. The Scaleway platform autoscales the number of available instances of your container to match the incoming load, depending on the settings you define here.
38-
- Define any **environment variables** you want to inject into your container. For each environment variable, click **+Add new variable** and enter the key/value pair.
39-
- Add **secrets** for your container. Secrets are environment variables which are injected into your container, but the values are not retained or displayed by Scaleway after initial validation.
40-
- Set the desired **privacy policy** for your container. This defines whether container invocation may be done anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**).
41-
- Click **Advanced Options** if you wish to set a custom timeout for your container.
42-
5. Click **Deploy container** to save any changes you have made.
35+
- Choose the [port](/serverless-containers/concepts/#port) your container is listening on. We recommend configuring your container to listen on the **PORT** environment variable.
36+
5. In the **Resources** section, select the vCPU and memory to allocate to your container at runtime. These values define the performance characteristics of your container.
37+
6. Set your [autoscaling](/serverless-containers/) preferences, or leave them at default values. The Scaleway platform automatically scales the number of available instances of your container to match the incoming load, depending on the settings you define here.
38+
7. In the **Advanced options** section, check or edit any of the following:
39+
<Tabs>
40+
<TabsTab label="Data">
41+
- Declare [environment variables](/serverless-containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair.
42+
- Declare [secrets](/serverless-containers/concepts/#secrets) for your container. Secrets are environment variables that are injected into your container, but the values are not retained or displayed by Scaleway after initial validation.
43+
<Message type="note">
44+
Encode your environment variables and secrets to `base64` if they are too large, and contain carriage returns.
45+
</Message>
46+
</TabsTab>
47+
<TabsTab label="Security">
48+
- Set the desired [privacy policy](/serverless-containers/concepts/#privacy-policy) for your container. This defines whether container invocation may be done anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**).
49+
- Tick the box under **HTTPS connections only** to prevent your container from being called from insecure HTTP connections.
50+
</TabsTab>
51+
<TabsTab label="Requests">
52+
- Set a custom [timeout](/serverless-containers/concepts/#timeout) for the duration of the requests received by your container.
53+
- Tick the box under [HTTP protocol](/serverless-containers/concepts/#protocol) to listen to HTTP/2 requests if it is required by your application. Otherwise, we recommend you use HTTP/1.
54+
</TabsTab>
55+
<TabsTab label="Performances">
56+
- Select a [sandbox](/serverless-containers/concepts/#sandbox) version:
57+
- Sandbox v2 for shorter cold starts (recommended).
58+
- Sandbox v1 if you require full compatibility with the Linux system call interface (legacy).
59+
</TabsTab>
60+
<TabsTab label="Health checks">
61+
- Update the [health check](/serverless-containers/concepts/#health-check) behavior according to your needs:
62+
- **Probe type**: TCP, or HTTP
63+
- **Health checks intervals**: 5s - 120s (default: 30s)
64+
- **Failure threshold**: 3 - 50 (default: 10)
65+
</TabsTab>
66+
<TabsTab label="Storage">
67+
- Modify the [ephemeral storage](/serverless-containers/concepts/#ephemeral-storage) according to your needs.
68+
</TabsTab>
69+
</Tabs>
70+
8. Click **Deploy container** to save any changes you have made.
4371

4472
### Manage a deployment from an external container registry
4573

4674
1. Click **Containers** in the **Serverless** section of the side menu. The Containers page displays.
4775
2. Click the relevant containers namespace.
48-
3. Click the name of the container you want to manage.
49-
4. Check or edit any of the following information as required, on the **Deployment** tab:
76+
3. Click the name of the container you want to manage, then select the **Settings** tab.
77+
4. In the **Container image** section:
5078
- Select the **External** container registry.
5179
- Enter the public container **image URL** provided by the external registry.
52-
- Choose the **Port** your container is listening on. We recommend configuring your container to listen on the **PORT** environment variable.
53-
- Choose the **resources** to be allocated to your container at runtime. These define the performance characteristics of your container.
54-
- Set your **scaling** preferences, or leave them at default values. The Scaleway platform autoscales the number of available instances of your container to match the incoming load, depending on the settings you define here.
55-
- Define any **environment variables** you want to inject into your container. For each environment variable, click **+Add new variable** and enter the key/value pair.
56-
- Add **secrets** for your container. Secrets are environment variables which are injected into your container, but the values are not retained or displayed by Scaleway after initial validation.
57-
- Set the desired **privacy policy** for your container. This defines whether container invocation may be done anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**).
58-
- Click **Advanced Options** if you wish to set a custom timeout for your container.
59-
5. Click **Deploy container** to save any changes you have made.
80+
- Choose the [port](/serverless-containers/concepts/#port) your container is listening on. We recommend configuring your container to listen on the **PORT** environment variable.
81+
5. In the **Resources** section, select the vCPU and memory to allocate to your container at runtime. These values define the performance characteristics of your container.
82+
6. Set your [autoscaling](/serverless-containers/) preferences, or leave them at default values. The Scaleway platform automatically scales the number of available instances of your container to match the incoming load, depending on the settings you define here.
83+
7. In the **Advanced options** section, check or edit any of the following:
84+
<Tabs>
85+
<TabsTab label="Data">
86+
- Declare [environment variables](/serverless-containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair.
87+
- Declare [secrets](/serverless-containers/concepts/#secrets) for your container. Secrets are environment variables that are injected into your container, but the values are not retained or displayed by Scaleway after initial validation.
88+
<Message type="note">
89+
Encode your environment variables and secrets to `base64` if they are too large, and contain carriage returns.
90+
</Message>
91+
</TabsTab>
92+
<TabsTab label="Security">
93+
- Set the desired [privacy policy](/serverless-containers/concepts/#privacy-policy) for your container. This defines whether container invocation may be done anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**).
94+
- Tick the box under **HTTPS connections only** to prevent your container from being called from insecure HTTP connections.
95+
</TabsTab>
96+
<TabsTab label="Requests">
97+
- Set a custom [timeout](/serverless-containers/concepts/#timeout) for the duration of the requests received by your container.
98+
- Tick the box under [HTTP protocol](/serverless-containers/concepts/#protocol) to listen to HTTP/2 requests if it is required by your application. Otherwise, we recommend you use HTTP/1.
99+
</TabsTab>
100+
<TabsTab label="Performances">
101+
- Select a [sandbox](/serverless-containers/concepts/#sandbox) version:
102+
- Sandbox v2 for shorter cold starts (recommended).
103+
- Sandbox v1 if you require full compatibility with the Linux system call interface (legacy).
104+
</TabsTab>
105+
<TabsTab label="Health checks">
106+
- Update the [health check](/serverless-containers/concepts/#health-check) behavior according to your needs:
107+
- **Probe type**: TCP, or HTTP
108+
- **Health checks intervals**: 5s - 120s (default: 30s)
109+
- **Failure threshold**: 3 - 50 (default: 10)
110+
</TabsTab>
111+
<TabsTab label="Storage">
112+
- Modify the [ephemeral storage](/serverless-containers/concepts/#ephemeral-storage) according to your needs.
113+
</TabsTab>
114+
</Tabs>
115+
8. Click **Deploy container** to save any changes you have made.
60116

61117

0 commit comments

Comments
 (0)