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.

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

feat(serverless): faq small fixes #3406

Merged
merged 5 commits into from
Jul 2, 2024
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
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
9 changes: 7 additions & 2 deletions faq/serverless-containers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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 support Virtual Private Networks yet but you can use the Scaleway IP ranges defined in the following link that can be used on Managed Databases and other products that allow IP Filtering: https://www.scaleway.com/en/peering/](https://www.scaleway.com/en/peering/).
thomas-tacquet marked this conversation as resolved.
Show resolved Hide resolved

## How can I deploy my Containers?

Expand All @@ -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 ?

thomas-tacquet marked this conversation as resolved.
Show resolved Hide resolved
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 DB), 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.
2 changes: 1 addition & 1 deletion faq/serverless-functions.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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 support Virtual Private Networks yet but you can use the Scaleway IP ranges defined in the following link that can be used on Managed Databases and other products that allow IP Filtering: https://www.scaleway.com/en/peering/](https://www.scaleway.com/en/peering/).
thomas-tacquet marked this conversation as resolved.
Show resolved Hide resolved

## How can I deploy my Functions?

Expand Down
10 changes: 1 addition & 9 deletions serverless/containers/troubleshooting/common-errors.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down
Loading