chore(serverless): concepts general update#6171
Open
thomas-tacquet wants to merge 2 commits intomainfrom
Open
Conversation
| 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. |
Collaborator
There was a problem hiding this comment.
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). |
Collaborator
There was a problem hiding this comment.
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). |
Collaborator
There was a problem hiding this comment.
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. |
Collaborator
There was a problem hiding this comment.
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. |
jcirinosclwy
approved these changes
Feb 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Your checklist for this pull request
Description
Please describe what you added or changed.