Skip to content

fix(deploy): use FQDN for SpiceDB endpoint in stage #441

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jsell-rh merged 1 commit into from
Apr 23, 2026
Merged

fix(deploy): use FQDN for SpiceDB endpoint in stage #441

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions deploy/apps/kartograph/overlays/stage/configmap-patch.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ metadata:
name: kartograph-config
data:
# Stage-specific overrides (merged with base)
# FQDN required for TLS cert SAN matching (service cert issued for kartograph-spicedb.kartograph-stage.svc)
SPICEDB_ENDPOINT: "kartograph-spicedb.kartograph-stage.svc:50051"
KARTOGRAPH_CORS_ORIGINS: "https://kartograph-stage.devshift.net,https://kartograph-dev-ui-kartograph-stage.apps.rosa.appsres09ue1.24ep.p3.openshiftapps.com"
# Dev UI
DEV_UI_API_BASE_URL: "https://kartograph-api-kartograph-stage.apps.rosa.appsres09ue1.24ep.p3.openshiftapps.com"
Expand Down
Loading