docs(srv): update

Author: SamyOubouaziz

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

@@ -40,16 +40,38 @@ You can deploy a container from the [Scaleway Container Registry](/container-reg
         <Message type="note">
         Available memory depends on allocated vCPU, and the maximum ephemeral storage value depends on allocated memory.
         </Message>
-    - Set your [scaling](/serverless-containers/concepts/#scaling) 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.
-    - Click **Advanced options** to define any [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.
-    - Add [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.
-        <Message type="note">
-        Encode your environment variables and secrets to `base64` if they are too large, and contain carriage returns.
-        </Message>
-    - 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**).
-    - Set a custom [timeout](/serverless-containers/concepts/#timeout) for your container.
-    - Verify the **estimated cost**.
-5. Click **Deploy container** to finish.
+5. Set your [autoscaling](/serverless-containers/concepts/#autoscaling) preferences:
+    - **Request concurrency**: your container automatically scales up/down within the minimum and maximum values entered based on the number of concurrent request received on each active instance of your container.
+    - **CPU percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the CPU load.
+    - **RAM percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the RAM used.
+6. In the **Advanced options** section set the following:
+    <Tabs>
+    <TabsTab label="Data">
+    - 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.
+    - 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.
+          <Message type="note">
+          Encode your environment variables and secrets to `base64` if they are too large, and contain carriage returns.
+          </Message>
+    </TabsTab>
+    <TabsTab label="Security">
+      - 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**).
+      - Tick the box under **HTTPS connections only** to prevent your container from being called from insecure HTTP connections.
+    </TabsTab>
+    <TabsTab label="Requests">
+    - Set a custom [timeout](/serverless-containers/concepts/#timeout) for the duration of the requests received by your container.
+    - 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.
+    </TabsTab>
+    <TabsTab label="Performances">
+    - Select a [sandbox](/serverless-containers/concepts/#sandbox) version:
+        - Sandbox v2 for shorter cold starts (recommended).
+        - Sandbox v1 if you require full compatibility with the Linux system call interface (legacy).
+    </TabsTab>
+    <TabsTab label="Storage">
+    - Modify the [ephemeral storage](/serverless-containers/concepts/#ephemeral-storage) according to your needs.
+    </TabsTab>
+    </Tabs>
+7. Verify the **estimated cost**.
+8. Click **Deploy container** to finish.
 
 ## Deploy from an external container registry
 
@@ -75,13 +97,35 @@ Private external container registries are currently not supported.
         <Message type="note">
         Available memory depends on allocated vCPU, and maximum ephemeral storage value depends on allocated memory.
         </Message>
-    - Set your [scaling](/serverless-containers/concepts/#scaling) 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.
-    - Click **Advanced options** to define any [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.
-    - Add [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.
-        <Message type="note">
-        Encode your environment variables and secrets to `base64` if they are too large, and contain carriage returns.
-        </Message>
-    - 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**).
-    - Set a custom [timeout](/serverless-containers/concepts/#timeout) for your container.
-    - Verify the **estimated cost**.
-5. Click **Deploy container** to finish.
+5. Set your [autoscaling](/serverless-containers/concepts/#autoscaling) preferences:
+    - **Request concurrency**: your container automatically scales up/down within the minimum and maximum values entered based on the number of concurrent request received on each active instance of your container.
+    - **CPU percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the CPU load.
+    - **RAM percentage**: your container automatically scales up/down within the minimum and maximum values entered based on the RAM used.
+6. In the **Advanced options** section set the following:
+    <Tabs>
+    <TabsTab label="Data">
+    - 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.
+    - 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.
+          <Message type="note">
+          Encode your environment variables and secrets to `base64` if they are too large, and contain carriage returns.
+          </Message>
+    </TabsTab>
+    <TabsTab label="Security">
+      - 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**).
+      - Tick the box under **HTTPS connections only** to prevent your container from being called from insecure HTTP connections.
+    </TabsTab>
+    <TabsTab label="Requests">
+    - Set a custom [timeout](/serverless-containers/concepts/#timeout) for the duration of the requests received by your container.
+    - 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.
+    </TabsTab>
+    <TabsTab label="Performances">
+    - Select a [sandbox](/serverless-containers/concepts/#sandbox) version:
+        - Sandbox v2 for shorter cold starts (recommended).
+        - Sandbox v1 if you require full compatibility with the Linux system call interface (legacy).
+    </TabsTab>
+    <TabsTab label="Storage">
+    - Modify the [ephemeral storage](/serverless-containers/concepts/#ephemeral-storage) according to your needs.
+    </TabsTab>
+    </Tabs>
+7. Verify the **estimated cost**.
+8. Click **Deploy container** to finish.