Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(serverless): add entries in serverless FAQ #3858

Merged
merged 2 commits into from
Oct 21, 2024
Merged

docs(serverless): add entries in serverless FAQ #3858

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b1ffb2d
docs(serverless): add entries in serverless FAQ
Bemilie Oct 18, 2024
4977ab0
fix: review changes
Bemilie Oct 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions faq/serverless-containers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,3 +126,13 @@ Scaleway Serverless Containers does not currently support Scaleway VPC or Privat

To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses.

## How can I attach Block Storage to a Serverless Container?

Scaleway Serverless Containers do not currently support attaching block storage. These containers are designed to be
stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external
solutions like Scaleway Object Storage.

# Why does my container have an instance running after deployment, even with min-scale 0?

Currently, a new container instance will always start after each deployment, even if there is no traffic and the minimum
scale is set to 0. This behavior is not configurable at this time.
11 changes: 11 additions & 0 deletions faq/serverless-functions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,3 +173,14 @@ Upgrading a runtime is highly recommended in case of deprecation, and for runtim
Scaleway Serverless Functions does not currently support Scaleway VPC or Private Networks, though this feature is under development.

To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Note that Serverless resources do not have dedicated or predictable IP addresses.

## How can I attach Block Storage to a Serverless Function?

Scaleway Serverless Functions do not currently support attaching block storage. These functions are designed to be
stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external
solutions like Scaleway Object Storage.

# Why does my function have an instance running after deployment, even with min-scale 0?

Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum
scale is set to 0. This behavior is not configurable at this time.