Welcome to ForgeOps
The Ping Identity Platform provides ForgeOps to help you deploy PingAM, PingDS, PingIDM, and PingGateway collectively in an integrated manner on a cloud platform that runs Kubernetes.
ForgeOps comprises mainly two sets of resources:
- The forgeops repository
-
The repository contains artifacts that let you get a sample Ping Identity Platform deployment up and running quickly. After you get the out-of-the-box deployment running, you can tailor it to explore how you might configure your Kubernetes cluster before you deploy the platform in production.
ForgeOps deployments have the following characteristics:
The ForgeOps documentation helps you work with ForgeOps deployments:
-
Tells you how you can quickly create a Kubernetes cluster on Google Cloud, Amazon Web Services (AWS), or Microsoft Azure, deploy the Ping Identity Platform, and access components in the deployment.
-
Contains how-tos for preparing for production deployments by customizing monitoring, setting alerts, backing up and restoring directory data, modifying the default security configuration, and running lightweight benchmarks to test DS, AM, and IDM performance.
-
Tells you how to modify the AM and IDM configurations in ForgeOps deployments and create customized Docker images for the Ping Identity Platform.
Chapters in this documentation
Start Here
Important considerations for a ForgeOps deployment.
Support
Support options for ForgeOps deployments.
Repositories
How to use the artifacts in ForgeOps public repositories.
Setup
Create a Kubernetes cluster suitable for a ForgeOps deployment.
Deploy
Deploy the platform on a Kubernetes cluster.
Customize
Customize AM and IDM configurations.
Prepare for production
PingGateway, monitoring, security, and benchmarking.
Backup
Backup and restore your data.
Upgrade
Upgrade the platform to a new version or apply a patch upgrade.
Troubleshoot
Tools and techniques to troubleshoot problems with ForgeOps deployments.
Reference
Command references, glossary, articles beyond the docs.