File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -487,15 +487,22 @@ import { readEnv } from "@/appExtensions";
487487const apiUrl = readEnv("EXTENSION_EXAMPLE_API_URL", "https://api.example.test");
488488```
489489
490- **Set it in a deployment** through the chart's `ui.env`:
490+ **Set it in a deployment** by getting the variable into the UI container's
491+ environment. With the `kagent` chart that is `ui.env`, which is passed through to
492+ the UI deployment verbatim:
491493
492494```yaml
495+ # values.yaml
493496ui:
494497 env:
495498 - name: EXTENSION_EXAMPLE_API_URL
496499 value: https://api.example.test
497500```
498501
502+ Any other chart works the same way — the only requirement is that the pod running
503+ the UI has the variable set. Nothing reads it from Kubernetes directly; the
504+ container's own startup script reads its environment.
505+
499506**Set it locally** in `ui/.env`, which is git-ignored — `.env.example` keeps a
500507section at the bottom for exactly this, so a branch that installs an extension
501508appends rather than editing the application's own settings above it:
You can’t perform that action at this time.
0 commit comments