MasterMito/work-club-manager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Fix Keycloak URL in K8s ConfigMap to use correct NodePort 30808
CI Pipeline / Backend Build & Test (push) Successful in 57s
Details
CI Pipeline / Frontend Lint, Test & Build (push) Successful in 34s
Details
CI Pipeline / Infrastructure Validation (push) Successful in 4s
Details

Browse Source 
- Changed api-base-url from :5001 to :30501
- Changed keycloak-url from :8080 to :30808
- Changed keycloak-authority from :8080 to :30808

The frontend was trying to connect to port 8080 which is not exposed
externally. Keycloak is accessible via NodePort 30808.
This commit is contained in:
WorkClub Automation
2026-03-21 08:27:05 +01:00
parent fd2931e59c
commit 86c7b0d46d
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
infra/k8s/base/configmap.yaml
+3 -3
View File
@@ -7,9 +7,9 @@ metadata:
data:
log-level: "Information"
cors-origins: "http://localhost:30080,http://192.168.240.200:30080,http://192.168.240.200:30808"
api-base-url: "http://192.168.240.200:5001"
keycloak-url: "http://192.168.240.200:8080"
keycloak-authority: "http://192.168.240.200:8080/realms/workclub"
api-base-url: "http://192.168.240.200:30501"
keycloak-url: "http://192.168.240.200:30808"
keycloak-authority: "http://192.168.240.200:30808/realms/workclub"
keycloak-audience: "workclub-api"
keycloak-realm: "workclub"