CDM Deployment

Now that you’ve set up your deployment environment following the instructions in the Environment Setup section for your cloud platform, you’re ready to deploy the CDM. This page shows you how to deploy the CDM in your Kubernetes cluster using artifacts from the forgeops repository.

Perform the following procedure:

Deploy the CDM
  1. Initialize the staging area for configuration profiles with the canonical CDK configuration profile [1] for the ForgeRock Identity Platform:

    $ cd /path/to/forgeops/bin
    $ ./config.sh init --profile cdk --version 7.0

    The config.sh init command copies the canonical CDK configuration profile from the master directory for configuration profiles to the staging area:

    The staging area is initialized from the canonical CDK profile.

    For more information about the management of ForgeRock Identity Platform configuration profiles in the forgeops repository, see Configuration Profiles.

  2. Change to the /path/to/forgeops directory and execute the skaffold run command:

    $ cd /path/to/forgeops
    $ skaffold run -p medium
  3. Make the prod namespace your current namespace:

    $ kubens prod
  4. Check the status of the pods in the prod namespace until all the pods are ready:

    1. Run the kubectl get pods command:

      $ kubectl get pods
      NAME                         READY   STATUS     RESTARTS   AGE
      admin-ui-6989d76f87-qwfxz    1/1     Running    0          1m1s
      am-9758bc5fd-hndsg           1/1     Running    0          2m37s
      am-9758bc5fd-qr124           1/1     Running    0          3m51s
      am-9758bc5fd-a6ccs           1/1     Running    0          3m51s
      amster-f7dpg                 0/1     Completed  0          3m
      ds-cts-0                     1/1     Running    0          2m36s
      ds-cts-1                     1/1     Running    0          114s
      ds-cts-2                     1/1     Running    0          70s
      ds-idrepo-0                  1/1     Running    0          2m36s
      ds-idrepo-1                  1/1     Running    0          112s
      ds-idrepo-2                  1/1     Running    0          74s
      end-user-ui-579d784b4-phk2v  1/1     Running    0          1m1s
      forgeops-secrets-k82w7       0/1     Completed  0          2m35s
      idm-0                        1/1     Running    0          2m28s
      idm-1                        1/1     Running    0          4m02s
      ldif-importer-l2d04          0/1     Completed  0          2m10s
      login-ui-78f44b644f-6srjg    1/1     Running    0          1m
    2. Review the output. Deployment is complete when:

      • All entries in the STATUS column indicate Running or Completed.

      • The READY column indicates all running containers are available. The entry in the READY column represents [total number of containers/number of available containers].

      • Three AM and two IDM pods are present.

      • The initial loading jobs (amster, forgeops-secret, and ldif-importer) have reached Completed status.

    3. If necessary, continue to query your deployment’s status until all the pods are ready.


1. The CDM and the CDK both use the CDK canonical configuration profile.