Skip to content

About

Self-service active/active Keycloak on OpenShift with AAP, ACM and GitOps. Automated IPv6 networking, Vault integration, HAProxy, DNS and deployment lifecycle.

Resources

Stars

3 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Active/Active Keycloak — one sign-in address, two active sites, deployment through AAP, ACM and GitOps

Active/Active Keycloak

Self-service identity infrastructure for two OpenShift sites.
One public endpoint · Shared PostgreSQL · IPv6 · GitOps

Deployment: verified Removal: verified HA acceptance: Runbook provided

Reference implementation status · Static badges, not live monitoring

Configure · Deploy · Survey · Architecture · Remove · Readiness


Community Keycloak 26.8.1 runs in stateless mode on two OpenShift 4.22.x clusters with a shared PostgreSQL database. OPNsense HAProxy sends IPv6 HTTPS traffic to healthy sites. AAP coordinates deployment through the ACM hub and Argo CD, reusing existing MetalLB, cert-manager and Vault/ESO integrations.

Public starter configuration. Source, manifests, diagrams and JSON use examples or placeholders. Deployment and removal are disabled by default. Start with the configuration guide to prepare your private deployment fork; keep credentials in Vault and AAP.

Built with

Technology logos: Keycloak, OpenShift, Ansible, Argo CD, OPNsense, PostgreSQL, Vault and Cloudflare

Existing MetalLB, cert-manager and External Secrets Operator integrations provide backend addresses, certificates and Kubernetes Secrets. Logo sources and asset notes.

Choose your next step

I want to… Start here
Configure the JSON files and platform Configuration guide
Deploy a new Keycloak instance Deployment guide
Understand or fill out the survey Seven deployment inputs
Connect an application Client flow and endpoints
Retry a failed workflow Troubleshooting and retry
Remove an installation Removal guide
Test high availability HA acceptance plan
Prepare another platform Platform setup and ACM integration

How traffic reaches Keycloak

IPv6 clients connect through Cloudflare DNS and OPNsense HAProxy to two Keycloak sites sharing PostgreSQL; AAP, ACM, GitOps and Vault manage deployment separately

View full-size architecture

  1. The client resolves auth.example.com through Cloudflare DNS.
  2. It connects directly to the OPNsense IPv6 VIP on HTTPS/443. Cloudflare is DNS-only.
  3. HAProxy terminates client TLS and opens a verified TLS connection to a healthy site's MetalLB service.
  4. Keycloak authenticates the request using the shared PostgreSQL database. Both sites present the same public issuer.

Clients need IPv6 connectivity and trust in the certificate issuer. Managed sites are IPv6-only; the ACM/AAP hub can be dual stack. Availability also depends on the database and edge infrastructure.

Deploy with seven inputs

After platform configuration and commissioning, open Keycloak Active Active Self Service in AAP and launch a new job.

Survey input Example
Managed cluster A cluster-a
Managed cluster B cluster-b
Public FQDN auth.example.com
Public IPv6 VIP PUBLIC_IPV6_VIP
Namespace on both sites keycloak
Vault database secret path global/tenant-a/postgresql
PostgreSQL TLS enabled when your database supports trusted TLS; otherwise explicitly choose disabled

The workflow runs Discover → Plan → Deploy. It discovers backend addresses and existing integrations, installs Keycloak on both sites, configures the project’s HAProxy objects, verifies authentication, and publishes the owned DNS record. Supply an existing dedicated database; the workflow does not create it. Each independent installation needs its own namespace, hostname, VIP and database.

You do not need to enter managed-cluster passwords, MetalLB backend IPs, router source networks or a bootstrap administrator Vault path. See the survey reference for discovery behavior and the exact secret schema.

How users sign in

Browser and application flow: redirect to Keycloak, authenticate, return an authorization code, exchange it for tokens, then use the application session

View full-size client journey

The example uses Authorization Code + PKCE. Browser sign-in and the application's token exchange use the same Keycloak hostname. Application traffic follows the application's own route. Client access explains the endpoints and TLS boundaries.

Validation status

The badges describe the private reference implementation. They do not query AAP or the clusters, and do not certify a new installation from this public copy.

Area Recorded status What it means
Deployment Verified The reference installation completed deployment workflows.
Removal Verified One deployed Keycloak installation was successfully removed, as confirmed by the user.
HA acceptance Runbook provided Test procedures and pass criteria are documented; execution and validation remain outstanding.
Certificate renewal Commissioning needed Deployment imports certificates; continuous edge renewal delivery is not yet scheduled.

See the readiness report for evidence and limits. A successful deployment does not establish production HA acceptance.

Explore the repository

Area Purpose
AAP automation Surveys, workflow registration and execution environment
ACM / hub resources Cluster selection, registration and GitOps permissions
Operator / site A / site B Kubernetes configuration
Argo Applications Operator, prerequisites and runtime per site
OPNsense / DNS template Edge and DNS integration
Environment, Vault, AAP credentials Platform inventory and credential requirements

Local preview

Render the Kubernetes configuration locally without contacting a cluster:

kubectl kustomize gitops/operator
kubectl kustomize gitops/keycloak/prerequisites
kubectl kustomize gitops/keycloak/overlays/cluster-a
kubectl kustomize gitops/keycloak/overlays/cluster-b

Raw manifests contain placeholders and platform-specific configuration. Use the automatic workflow to supply discovered values and coordinate synchronization. The diagrams are editable SVGs with no external image or font dependencies.


Two sites. One identity endpoint. Every change reviewed in Git.

About

Self-service active/active Keycloak on OpenShift with AAP, ACM and GitOps. Automated IPv6 networking, Vault integration, HAProxy, DNS and deployment lifecycle.

Resources

Stars

3 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages