You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/serverless-functions/faq.mdx
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -194,10 +194,12 @@ Integration is straightforward. Serverless Functions and Containers can be trigg
194
194
195
195
Serverless Functions namespaces and Container Registry namespaces observe the following behaviors:
196
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.
197
+
- Creating a Serverless Functions namespace implicitly creates an empty Container Registry namespace. When a Serverless Function is deployed, the built image will be stored in the Container Registry namespace created.
198
198
199
199
- Creating a Container Registry namespace **does not** create a Serverless Functions namespace.
200
200
201
+
- Deploying a function in a Serverless Functions namespace creates an image in the corresponding Container Registry namespace.
202
+
201
203
- 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.
0 commit comments