Configuring Typha

    • Manifest

    Configuration for Typha is read from one of two possible locations, in order, as follows.

    1. Environment variables, prefixed with .

    The value of any configuration parameter is the value read from the first location containing a value. For example, if an environment variable contains a value, it takes precedence.

    If not set in any of these locations, most configuration parameters have defaults, and it should be rare to have to explicitly set them.

    note

    By default, if the health endpoint is enabled Typha listens on localhost. However, if Typha is used in Kubernetes, the kubelet will do health checks using the pod IP. To work around this discrepancy, the Typha image supports a health-check CLI command that fetches the health endpoint: . If you modify the health port, you will need to add the --port=<port> argument to the liveness and readiness probe commands in the manifest.

    Environment variables

    For more information on how to use and set these variables, refer to .