From ddf8d7cbcbacdb3b1c277f7a3a1495034b386cf3 Mon Sep 17 00:00:00 2001 From: Josh Santos Date: Wed, 18 Dec 2024 21:24:37 +0700 Subject: [PATCH] Update environment variable name in kubernetes deployment docs Signed-off-by: Josh Santos --- docs/deployment/k8s.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/deployment/k8s.md b/docs/deployment/k8s.md index 46ba273e14..a2939dcae7 100644 --- a/docs/deployment/k8s.md +++ b/docs/deployment/k8s.md @@ -387,8 +387,8 @@ $ yarn build-image --tag backstage:1.0.0 ``` There is no special wiring needed to access the PostgreSQL service. Since it's -running on the same cluster, Kubernetes will inject `POSTGRES_SERVICE_HOST` and -`POSTGRES_SERVICE_PORT` environment variables into our Backstage container. +running on the same cluster, Kubernetes will inject `POSTGRES_HOST` and +`POSTGRES_PORT` environment variables into our Backstage container. These can be used in the Backstage `app-config.yaml` along with the secrets. Apply this to `app-config.production.yaml` as well if you have one: ```yaml @@ -396,8 +396,8 @@ backend: database: client: pg connection: - host: ${POSTGRES_SERVICE_HOST} - port: ${POSTGRES_SERVICE_PORT} + host: ${POSTGRES_HOST} + port: ${POSTGRES_PORT} user: ${POSTGRES_USER} password: ${POSTGRES_PASSWORD} ```