Deploying OpenIAM on Kubernetes using Helm
This guide describes how to deploy OpenIAM to a private (not AWS, GKE) Kubernetes cluster via Helm, but without Terraform. This type of deployment is not recommended due to the number of Helm variables.
If you are deploying to AWS or GKE, please use Terraform!
Prerequisites
First, run the following command to ensure that configmaps are created correctly. You only need to do this once, or when the underlying files change.
mkdir -p openiam-configmap/.ssl && mkdir -p openiam-configmap/.apache && cp -r .ssl/* openiam-configmap/.ssl/ && cp -r .apache/* openiam-configmap/.apache/
Deploying
We provide a working example of how to deploy OpenIAM via Helm. Please see setup-no-tf.sh. This contains all the required values for each helm chart that we deploy.
Migration guide
Versions pre-4.2.1 to 4.2.1
We've updated our vault datastore in 4.2.1. To migrate, please follow the steps below.
- Deploy with the
openiam.vault.migrateterraform variable set totrue, when deployingopeniam-vaultandopeniam. - Wait for all pods to come up.
- Redeploy with the
vault.migrateterraform variable set tofalse, when deployingopeniam-vaultandopeniam. - Wait for all pods to come up.