Skip to content

chore(serverless): concepts general update#6171

Open
thomas-tacquet wants to merge 2 commits intomainfrom
serverless-concepts-update
Open

chore(serverless): concepts general update#6171
thomas-tacquet wants to merge 2 commits intomainfrom
serverless-concepts-update

Conversation

@thomas-tacquet
Copy link
Collaborator

Your checklist for this pull request

Description

Please describe what you added or changed.

@thomas-tacquet thomas-tacquet self-assigned this Feb 9, 2026
@thomas-tacquet thomas-tacquet requested review from a team as code owners February 9, 2026 16:54
@thomas-tacquet thomas-tacquet added do not merge PR that shouldn't be merged before a specific date (eg release) product: serverless do not review yet please wait before reviewing its not ready yet labels Feb 9, 2026
Concurrency determines the number of incoming requests a single instance of a container can process before scaling up. Serverless Containers automatically scale according to the number of instances needed to handle the incoming workload.
Concurrency determines the number of incoming requests a single instance of a container can process before scaling up. Serverless Containers automatically scale according to the number of instances needed to handle the incoming workload.

Unlike Serverless Functions which handles only one request per instance, Serverless Containers is designed to handle multiple requests simultaneously within one container. This is a powerful feature for optimizing performance and reducing costs.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Unlike Serverless Functions which handles only one request per instance, Serverless Containers is designed to handle multiple requests simultaneously within one container. This is a powerful feature for optimizing performance and reducing costs.
Unlike Serverless Functions, which handles only one request per instance, Serverless Containers is designed to handle multiple requests simultaneously within one container. This is a powerful feature for optimizing performance and reducing costs.


If a variable is defined in both your `Dockerfile` and Servlerless Containers service, the Serverless Containers configuration takes precedence.

For sensitive information we encourage to use [Secret environment variables](/serverless-containers/concepts/#secrets).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For sensitive information we encourage to use [Secret environment variables](/serverless-containers/concepts/#secrets).
For sensitive information, we encourage you to use [Secret environment variables](/serverless-containers/concepts/#secrets).


Some names are reserved. [See details on reserved names](/serverless-functions/reference-content/functions-limitations/#configuration-restrictions).

For sensitive information we encourage to use [Secret environment variables](/serverless-functions/concepts/#secrets).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For sensitive information we encourage to use [Secret environment variables](/serverless-functions/concepts/#secrets).
For sensitive information, we encourage you to use [Secret environment variables](/serverless-functions/concepts/#secrets).

## Secrets

Secrets are an extra-secure type of environment variable. They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation.
Secrets are an extra-secure type of [environment variable]((/serverless-functions/concepts/#environment-variables). They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Secrets are an extra-secure type of [environment variable]((/serverless-functions/concepts/#environment-variables). They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation.
Secrets are an extra-secure type of [environment variable](/serverless-functions/concepts/#environment-variables). They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge PR that shouldn't be merged before a specific date (eg release) do not review yet please wait before reviewing its not ready yet product: serverless

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants