Skip to content

chore(k8s): wire prod Keycloak config and real CORS origin#209

Merged
vredchenko merged 1 commit into
mainfrom
chore/k8s-prod-keycloak-and-cors
May 26, 2026
Merged

chore(k8s): wire prod Keycloak config and real CORS origin#209
vredchenko merged 1 commit into
mainfrom
chore/k8s-prod-keycloak-and-cors

Conversation

@vredchenko
Copy link
Copy Markdown
Collaborator

Summary

Two prod-deploy blockers fixed in k8s/environments/production/configmap.yaml:

  1. CORS_ALLOWED_ORIGINS was the https://app.example.com placeholder. Set to the real prod ingress hostname https://smartem.diamond.ac.uk (matches production/ingress.yaml).
  2. No Keycloak config at all in prod. Backend is always-on auth (smartem-decisions#285) so without this the prod backend will 403 every non-exempt request. Added:
    • KEYCLOAK_URL: https://identity.diamond.ac.uk
    • KEYCLOAK_ALLOWED_AZP: SmartEM_User,SmartEM_Agent

KEYCLOAK_REALM and KEYCLOAK_VERIFY_ISS left as TODO comments pending confirmation from DLS Keycloak admins (per "verify or omit" rule for DLS-facing config).

Test plan

  • DLS Keycloak admins confirm realm name; backfill KEYCLOAK_REALM and KEYCLOAK_VERIFY_ISS: "true" before go-live
  • Once SmartEM_User + SmartEM_Agent clients exist in prod realm, smoke-test backend with a token from each

Replaces the app.example.com placeholder with the real prod ingress
hostname (smartem.diamond.ac.uk) and adds the Keycloak block so the
backend will accept tokens once the DLS production Keycloak clients
exist.

KEYCLOAK_REALM and KEYCLOAK_VERIFY_ISS are intentionally left as TODOs
pending confirmation from DLS Keycloak admins.
@github-actions github-actions Bot added the devops CI/CD, deployment, infrastructure, or tooling work label May 26, 2026
@vredchenko vredchenko merged commit 3a5e71b into main May 26, 2026
7 checks passed
@vredchenko vredchenko deleted the chore/k8s-prod-keycloak-and-cors branch May 26, 2026 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

devops CI/CD, deployment, infrastructure, or tooling work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant