pod.portfield of your API configuration (default: 8080).
hello-world, a request to
<load_balancer_url>/hello-worldwill be routed to the root (
/) of your web server, and a request to
<load_balancer_url>/hello-world/subpatchwill be routed to
/subpathon your web server.
tiangolo/uvicorn-gunicorn-fastapibehaves this way). Readiness checks ensure that traffic is not sent into your web server before it's ready to handle them.
exec(see API configuration for usage instructions). A simple and often effective approach is to add a route to your web server (e.g.
/healthz) which responds with status code 200, and configure your readiness probe accordingly:
/mntdirectory is mounted to each container's file system, and is shared across all containers.
/cortex/client/cli.yaml, which is configured to connect to the cluster. In addition, the
CORTEX_CLI_CONFIG_DIRenvironment variable is set to
/cortex/clientby default. Therefore, no additional configuration is required to use the CLI or Python client (which can be instantiated via
<api_name>is the name of the Realtime API you are making a request to.
hello-worldrunning in the cluster, you can make a request to it from a different API in Python by using:
target_in_flight) should be modified with the understanding that requests will be considered "in-flight" in the first API as the request is being fulfilled by the second API.