Skip to content

chore(serverless_containers): update 502 docs to reflect Console avai… #5000

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

Merged
merged 1 commit into from
May 21, 2025
Merged

chore(serverless_containers): update 502 docs to reflect Console avai… #5000

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
21 changes: 3 additions & 18 deletions pages/serverless-containers/troubleshooting/502-error-when-scaling.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,21 +27,6 @@ This issue typically occurs when traffic is sent too early to the newly created

To ensure the Serverless Container is completely ready, both in terms of the HTTP port and the software scope, it is recommended to use **custom health checks**.

You can configure [Custom health checks via the Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-containers-update-an-existing-container) with the `health_check` parameter. In this case, we recommend you implement a custom HTTP route on the Container that returns its readiness status.

<Message type="tip">
A simple health check to implement is just a simple `GET` on `/` to make sure the HTTP server is properly listening.

Example (incomplete) settings:
```
health_check: {
http: {
path: "/"
}
}
```
</Message>

<Message type="note">
Custom healthcheck feature will be available in the Scaleway console for Q1 2025.
</Message>
Custom health checks allow you to define a specific endpoint that the Serverless Container must respond to before it is considered ready to receive traffic. This ensures that the container is fully initialized and ready to handle requests.

Update your Serverless Container to use custom health checks by following the instructions in the [Serverless Containers documentation](/serverless-containers/how-to/manage-a-container/#how-to-manage-a-container-deployment).