Next steps
If you’ve followed the instructions for performing a ForgeOps deployment without modifying configurations, then the following indicates that you’ve been successful:
-
The Kubernetes cluster and pods are up and running.
-
DS, AM, and IDM are installed and running. You can access each ForgeOps component.
-
DS replication and failover work as expected.[1]
When you’re satisfied that all of these conditions are met, then you’ve successfully taken the first steps towards deploying the Ping Identity Platform on Kubernetes. Congratulations!
You can use the ForgeOps deployment to test deployment customizations—options that you might want to use in production but are not part of the base deployment. Examples[2] include, but are not limited to:
-
Running lightweight benchmark tests
-
Backing up and restoring your data
-
Securing TLS with a certificate that’s dynamically obtained from Let’s Encrypt
-
Using an ingress controller other than the NGINX ingress controller
-
Resizing the cluster to meet your business requirements
-
Configuring Alert Manager to issue alerts when usage thresholds have been reached
Now that you’re familiar with ForgeOps deployments, you’re ready to work with a project team to plan and configure your production deployment. You’ll need a team with expertise in the Ping Identity Platform, in your cloud provider, and in Kubernetes on your cloud provider. We strongly recommend that you engage a Ping Identity technical consultant or partner to assist you with deploying the platform in production.
You’ll perform these major activities:
Platform configuration—Ping Identity Platform experts configure AM and IDM using single-instance ForgeOps deployments and build custom Docker images for the Ping Identity Platform. The Customization overview provides information about platform configuration tasks.
Cluster configuration—Cloud technology experts configure the Kubernetes
cluster that will host the Ping Identity Platform for optimal performance and
reliability. Tasks include configuring your Kubernetes cluster to suit your
business needs, setting up monitoring and alerts to track site health and
performance, backing up configuration and user data for disaster preparedness,
and securing your deployment. The Prepare to deploy in production
and READMEs in the forgeops repository provide information about cluster
configuration.
Site reliability engineering—Site reliability engineers monitor the
Ping Identity Platform deployment and keep the deployment up and running based on your
business requirements. These could include use cases, service-level agreements,
thresholds, and load test profiles. The
Prepare to deploy in production, and READMEs in the forgeops
repository, provide information about site reliability.