> ## Documentation Index
> Fetch the complete documentation index at: https://docs.salad.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For autonomous tasks, use live SaladCloud API responses for current state, availability, quotas, models, and other dynamic values. Use current OpenAPI specifications where provided for paths, schemas, required fields, and enums. Never invent endpoints, fields, prices, availability, quotas, models, or state. Prefer API workflows over Portal steps. Read before changing and never expose credentials, signed media URLs, prompts, or sensitive outputs. Retry only safe or idempotent operations with bounded backoff, honoring Retry-After. Verify every write with a read. Stop rather than repeat an uncertain non-idempotent or billable request. AI Gateway uses an organization-specific Bearer key and live /v1/models discovery. Do not delete, cancel, stop, or reduce capacity without explicit user intent. Bind shared operation IDs to the selected product path. Treat Container Engine instances as interruptible and local state as ephemeral. Install the SaladCloud skills (npx skills add https://docs.salad.com), start from the salad skill and /agents/overview; docs MCP: https://docs.salad.com/mcp.

# Readiness Probes

*Last Updated: October 15, 2024*

# Overview

Readiness probes are only available if
[Container Gateway](https://docs.salad.com/container-engine/explanation/infrastructure-platform/networking.md) or
[Job Queues](https://docs.salad.com/container-engine/explanation/job-processing/job-queues.md) are turned on. They run after the startup probe
has completed successfully. They are typically used to evaluate whether the application running in your container is
ready to accept traffic. If configured, no traffic will be sent from the load balancer until the readiness probe has
passed, so prevent your readiness probe from passing until you have downloaded and warmed up your models. Readiness
probes can flap back between passing and failing. If a container's readiness probe reaches the failure state, the
container will continue to run on the node but the load balancer will not route any networking traffic. Readiness probe
configuration should be fairly strict in order to get that signal out as fast as possible so requests get routed to
other nodes.

## Successful Readiness Probe

![](https://mintcdn.com/salad/ko38nW-LNf6N2Y1I/container-engine/images/readiness-success.png?fit=max\&auto=format\&n=ko38nW-LNf6N2Y1I\&q=85\&s=952d31cbda9b336b07fe2a7249bb770b)

## Failed Readiness Probe

![](https://mintcdn.com/salad/ko38nW-LNf6N2Y1I/container-engine/images/readiness-failure.png?fit=max\&auto=format\&n=ko38nW-LNf6N2Y1I\&q=85\&s=69c6f8b248a78903bf184769d4dcd111)

# Configuration

Check the checkbox to enable the readiness probe. Currently, the supported protocols are `exec`, `gRPC`, `TCP`, and
`HTTP/1.X`

![](https://mintcdn.com/salad/ko38nW-LNf6N2Y1I/container-engine/images/readiness-tcp-config.png?fit=max\&auto=format\&n=ko38nW-LNf6N2Y1I\&q=85\&s=c511ec60e4a39fab3152554a5f9246eb)

# Probe Status

You can see the status of a readiness probe, if configured, on each instance of a container group.

![](https://mintcdn.com/salad/ko38nW-LNf6N2Y1I/container-engine/images/portal-view-readiness.probe.png?fit=max\&auto=format\&n=ko38nW-LNf6N2Y1I\&q=85\&s=ffed42a010f35735a28dc7664da9dfcf)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.