ForgeOps

Welcome to ForgeOps

The Ping Advanced Identity Software 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 Advanced Identity Software 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:

  • Fully integrated AM, IDM, and DS installations

  • Multi-zone high availability[1]

  • Replicated directory services[1]

  • Ingress configuration[2]

  • Certificate management

  • Randomly generated secrets with ability to rotate secrets

  • Prometheus monitoring, Grafana reporting, and alert management[1]

The ForgeOps documentation

The ForgeOps documentation helps you work with ForgeOps deployments:

Chapters in this documentation

Topic Description

Start Here

Important information to consider before you attempt a ForgeOps deployment.

Support

Support options for ForgeOps deployments.

Repositories

How to use the artifacts in ForgeOps public GitHub repositories.

Setup

Create a Kubernetes cluster suitable for a ForgeOps deployment.

Deploy

Deploy the platform on a Kubernetes cluster using ForgeOps.

Customize

Customize the platform by configuring AM and IDM.

Prepare for production

Base images, PingGateway, monitoring, security, benchmarking, and ingress.

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.
1. Not available on single-instance ForgeOps deployments.
2. Not available on ForgeOps deployments on minikube.