Skip to content

Commit 9686046

Browse files
committed
docs(srv): add content on serverless / CR namespaces behavior MTA-5959
1 parent 30889d2 commit 9686046

File tree

4 files changed

+31
-0
lines changed

4 files changed

+31
-0
lines changed

pages/serverless-containers/faq.mdx

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -173,6 +173,20 @@ Integration is straightforward. Serverless Functions and Containers can be trigg
173173

174174
You can copy an image from an external registry using the Docker CLI, or open source third-party tools such as [Skopeo](https://github.com/containers/skopeo). Refer to the [dedicated documentation](/serverless-containers/api-cli/migrate-external-image-to-scaleway-registry/) for more information.
175175

176+
### How do Serverless Containers namespaces and Container Registry namespaces interact?
177+
178+
Serverless Containers namespaces and Container Registry namespaces observe the following behaviors:
179+
180+
- Creating a Serverless Containers namespace implicitly creates an empty Container Registry namespace.
181+
182+
- Creating a Container Registry namespace **does not** create a Serverless Containers namespace.
183+
184+
- Serverless Containers and Container Registry namespace are not linked.
185+
186+
- With Serverless Containers, you can use images from any Container Registry namespace, as long as they are in the same [Project](/organizations-and-projects/concepts/#project).
187+
188+
- If you delete The Container Registry namespace associated with a Serverless Containers namespace, it will be created again when deploying a container within this Serverless Containers namespace.
189+
176190
### How do Serverless Containers health checks work ?
177191

178192
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 is important to run them before binding to the port (starting the webserver).

pages/serverless-containers/how-to/create-manage-delete-containers-namespace.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,10 @@ This page shows you how to create and manage a Serverless Containers namespace.
3333
- Verify the **estimated cost**.
3434
4. Click **Create namespace only** to finish, or click **Create namespace and add container** if you want to [deploy a container](/serverless-containers/how-to/deploy-container/) next.
3535

36+
<Message type="tip">
37+
Refer to the [dedicated FAQ](/serverless-containers/faq/#how-do-serverless-containers-namespaces-and-container-registry-namespaces-interact) for more information on how Serverless Containers namespaces and Container Registry namespaces interact.
38+
</Message>
39+
3640
## Managing a Serverless Containers namespace
3741

3842
### Generating and managing access tokens

pages/serverless-functions/faq.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -190,6 +190,16 @@ There are [several ways to deploy Serverless Functions](/serverless-functions/re
190190

191191
Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/messaging/concepts/#queues) and [Topics and Events](/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object-storage/), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
192192

193+
### How do Serverless Functions namespaces and Container Registry namespaces interact?
194+
195+
Serverless Functions namespaces and Container Registry namespaces observe the following behaviors:
196+
197+
- Creating a Serverless Functions namespace implicitly creates a Container Registry namespace. When a Serverless Function is deployed, the built image will be stored in the Container Registry namespace created.
198+
199+
- Creating a Container Registry namespace **does not** create a Serverless Functions namespace.
200+
201+
- If you delete The Container Registry namespace associated with a Serverless Functions namespace, it will be created again when deploying a function within this Serverless Functions namespace.
202+
193203
### How can I check build errors?
194204

195205
Some Serverless runtimes (ex: `Go`, `Rust`) will compile your code in order to make your function executable.

pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,9 @@ This page shows you how to create, manage, and delete a Functions namespace usin
3636
- Set optional secret environment variables. **Secrets** are environment variables which are injected into your function and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**.
3737
4. Click **Create namespace only** to finish, or click **Create namespace and add a function** if you want to [create a function](/serverless-functions/how-to/create-a-function/) next.
3838

39+
<Message type="tip">
40+
Refer to the [dedicated FAQ](/serverless-functions/faq/#how-do-serverless-containers-namespaces-and-container-registry-namespaces-interact) for more information on how Serverless Functions namespaces and Container Registry namespaces interact.
41+
</Message>
3942

4043
## Managing a Serverless Functions namespace
4144

0 commit comments

Comments
 (0)