Chapter 4. Migrating Templates deployments on Openshift

Procedure

1. Install Red Hat build of Keycloak Operator to the namespace.

2. Create new CRs and related Secrets.

   Manually migrate your template based Red Hat Single Sign-On 7.6 configuration to your new Kecyloak CR. See the following examples for suggested mappings between Template parameters and Keycloak CR fields.

   This example shows the Operator CR fields for Red Hat build of Keycloak.

   apiVersion: k8s.keycloak.org/v2alpha1
   kind: Keycloak
   metadata:
     name: rhbk
   spec:
     instances: 1
     db:
       vendor: postgres
       host: postgres-db
       usernameSecret:
         name: keycloak-db-secret
         key: username
       passwordSecret:
         name: keycloak-db-secret
         key: password
     http:
       tlsSecret: sso-x509-https-secret

   Copy to Clipboard Toggle word wrap

   This example shows the DeploymentConfig for a Red Hat Single Sign-On 7.6 Template

   apiVersion: apps.openshift.io/v1
   kind: DeploymentConfig
   metadata:
     name: rhsso
   spec:
     replicas: 1
     template:
       spec:
         volumes:
           - name: sso-x509-https-volume
             secret:
               secretName: sso-x509-https-secret
               defaultMode: 420
         containers:
             volumeMounts:
               - name: sso-x509-https-volume
                 readOnly: true
             env:
               - name: DB_SERVICE_PREFIX_MAPPING
                 value: postgres-db=DB
               - name: DB_USERNAME
                 value: username
               - name: DB_PASSWORD
                 value: password

   Copy to Clipboard Toggle word wrap