feat(serverless): faq small fixes (#3406)

* feat(serverless): faq fixes * add healthcheck notice * Apply suggestions from code review Co-authored-by: Rowena Jones <[email protected]> * Apply suggestions from code review Co-authored-by: nerda-codes <[email protected]> --------- Co-authored-by: Rowena Jones <[email protected]> Co-authored-by: nerda-codes <[email protected]>
scaleway · Jul 2, 2024 · cbcf937 · cbcf937
1 parent 1f78bba
commit cbcf937
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 12 deletions.
diff --git a/faq/serverless-containers.mdx b/faq/serverless-containers.mdx
@@ -81,7 +81,7 @@ Refer to our dedicated page about [Serverless Containers limitations and configu
 
 ## Can I whitelist the IPs of my containers?
 
-Some services need to filter IPs, for example, databases. Serverless Containers do not support Virtual Private Networks yet, but you can use the Scaleway IP ranges defined [here](http://as12876.net/).
+Serverless Containers does not yet support Private Networks. However, you can use the Scaleway IP ranges defined  at [https://www.scaleway.com/en/peering/](https://www.scaleway.com/en/peering/) on Managed Databases and other products that allow IP filtering.
 
 ## How can I deploy my Containers?
 
@@ -98,4 +98,9 @@ Protocol switching is currently not available in the console but can be changed
 
 ## Why does my gRPC container not respond?
 
-Containers use http1 by default, yet the gRPC protocol requires http2. You can upgrade the protocol to http2 (`h2c`).
+Containers use http1 by default, yet the gRPC protocol requires http2. You can upgrade the protocol to http2 (`h2c`).
+
+## How does Serverless Container healthcheck work ?
+
+A Serverless Container is set to `ready` once the specified port is correctly bound to the container, and will start receiving traffic. If your application needs to perform some tasks before receiving traffic (e.g. connect to a database), it's important to run them before binding to the port (starting the webserver).
+For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the healthcheck will be customizable for your applications.
diff --git a/faq/serverless-functions.mdx b/faq/serverless-functions.mdx
@@ -132,7 +132,7 @@ In the `Serverless Functions Logs` dashboard, you will then be able to read info
 
 ## Can I allow to list the IPs of my functions?
 
-Some services need to filter IPs, for example databases. Serverless Functions does not support Virtual Private Networks yet but you can use the Scaleway IP ranges defined in the following link: [http://as12876.net/](http://as12876.net/).
+Serverless Functions does not yet support Private Networks. However, you can use the Scaleway IP ranges defined  at [https://www.scaleway.com/en/peering/](https://www.scaleway.com/en/peering/) on Managed Databases and other products that allow IP filtering.
 
 ## How can I deploy my Functions?
 

diff --git a/serverless/containers/troubleshooting/common-errors.mdx b/serverless/containers/troubleshooting/common-errors.mdx
@@ -36,19 +36,11 @@ categories:
     ```
   </Message>
 
-## Unable to build
-
-### Possible solutions
-
-- Make sure that you used a public image from the [Docker Registry](https://docs.docker.com/registry/) or a compatible image from the [Scaleway Container Registry](/serverless/containers/how-to/deploy-a-container-from-scaleway-container-registry/).
-
-- Make sure the image is still available in the [Scaleway Container Registry](/containers/container-registry/concepts/#container-registry).
-
 ## Failed to create a namespace
 
 ### Cause
 
-This issue can happen for the following reasons: 
+This issue can happen for the following reasons:
 
 - You created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers)
 - You created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry)