ForgeOps

Deploy PingGateway

ForgeOps deployments don’t include PingGateway by default.

To deploy PingGateway after you’ve performed a ForgeOps deployment:

  1. Verify that the ForgeOps deployment is up and running.

  2. Set the active namespace in your local Kubernetes context to the namespace in which you’ve deployed the platform components.

  3. Set up your environment and deploy PingGateway:

    In Kustomize-based deployments

    1. Add the - ./ig line in the default overlay file, kustomize/overlay/my-env/kustomization.yaml:

      kind: Kustomization
apiVersion: kustomize.config.k8s.io/v1beta1
resources:
- ./base
- ./secrets
- ./ds-cts
- ./ds-idrepo
- ./am
- ./amster
- ./idm
- ./ig
- ./ds-set-passwords
- ./admin-ui
- ./end-user-ui
- ./login-ui

    2. Add PingGateway Docker image to your ForgeOps deployment configuration:

      $ cd /path/to/forgeops/bin/
$ ./forgeops image --release 2025.3.0 ig --env-name my-env

    3. Deploy PingGateway:

      $ /path/to/forgeops/bin/forgeops apply --env-name my-env ig
    In Helm-based deployments

    1. Deploy PingGateway using Helm:

      $ cd /path/to/forgeops
$ helm upgrade --install identity-platform ./ \
 --namespace my-namespace \
 --values /path/to/forgeops/helm/my-env/values.yaml

  4. Run the kubectl get pods command to check the status of the PingGateway pod. Wait until the pod is ready before proceeding to the next step.

  5. Verify that PingGateway is running:

    $ curl --insecure -L -X GET https://my-fqdn/ig/openig/ping -v

...
> GET /ig/openig/ping HTTP/2
> Host: my-fqdn
> User-Agent: curl/7.64.1
> Accept: /
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 200
< date: Thu, 29 Jul 2021 21:07:44 GMT
<
* Connection #0 to host my-fqdn left intact
* Closing connection 0

  6. Verify that the reverse proxy to the IDM pod is running:

    $ curl --insecure -L -X GET https://my-fqdn/ig/openidm/info/ping -v
...
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
...
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 200
...