Documentation ¶
Overview ¶
The runner for gcsrunner fetches an Envoy Config from GCS and writes it to a local file. It then starts Envoy using that new config. If this process receives a signal, it will be forward to the Envoy process. It is expected that this signal is intended to stop the process.
Two environment variables are required: `BUCKET` and `CONFIG_FILE_NAME`. Fetches from the bucket at `BUCKET` at the path `CONFIG_FILE_NAME`, Behavior is similar to running:
`gsutil cp "gs://${BUCKET}/${CONFIG_FILE_NAME}" envoy.json`
without needing `gsutil` in the image.
If RUN_AS_SERVICE_ACCOUNT is provided, gcsrunner will attempt to impersonate the given service account in the call to read from GCS.
Click to show internal directories.
Click to hide internal directories.