ForgeOps 2025.1 release notes

The Upgrade document section is updated to cover the new format of the forgeops command and the ForgeOps deployment environment. Learn more in the Upgrade Overview section.

The amster command has been subsumed in the forgeops amster command. Learn more in the Troubleshooting amster pod section.

You can set FORGEOPS_ROOT parameter to specify the local folder that contains the Docker, Helm, and Kustomize configurations. This allows you to keep your changes in a separate Git repository. You can create a ~/.forgeops.conf file with your overrides. Your development team can place a forgeops.conf file in their FORGEOPS_ROOT location which contains team-wide settings.

You can now get a list of supported platform releases and their latest flags using the forgeops info --list-releases command.

You can now define and update PingGateway node configuration parameters, such as CPU, memory, replicas, and pull policy in a ForgeOps deployment environmen. This lets you install PingGateway quickly in a ForgeOps deployment.

The version of pyyaml is updated. Run the [.command]forgeops configure# command to update your libraries.

The timestamp issue in the forgeops info --env-name has been fixed.

Helm pre-install hooks are now used to deploy DS certificates. These certificates are no longer deleted when Helm chart is uninstalled.

Updated the AM service in the Helm chart to use HTTPS target port.

Prometheus default ports and labels have been updated to match the new Helm chart.

The procedures to upgrade ForgeOps artifacts and component images are revised. Learn more in Upgrade Overview.

We’ve added sample storage class definition files required for ForgeOps deployment. This helps users who are setting up Kubernetes clusters without using the ForgeOps-provided Terraform manifests.

Because we’ve removed the forgeops-minikube script, we’ve revised the steps to create a Minikube cluster to use the generic minikube command. Learn more about creating a Minikube cluster here.

We’ve added the step to create the fast storage class required for ForgeOps deployment on Minikube.

Revised the procedure to perform ForgeOps deployment on Minikube using generic Kubernetes tools rather than propreitary forgeops-minikube utility.

The master branch of forgeops repository is no longer used. The ForgeOps artifacts are released from the main branch. The latest Docker images are tagged as dev images. You can view the available Docker images using the forgeops image command.

Ping Identity now supports ForgeOps-provided Docker images. We’ve revised the documentation and removed the "unsupported" admonition.

Removed the legacy docker/ds/idrepo and docker/ds/cts directories. The content that was in docker/ds/ds-new is now in docker/ds.

The ldif-importer component uses the DS Docker image, you don’t need to build a separate Docker image. The required ldif-importer scripts are mounted to the ldif-importer pod using a configmap.

The new forgeops command reference contains more information on the new forgeops command.

Learn more about the new ForgeOps release process here

Learn more about customizing DS image in the new section on Customizing DS image.

Learn more about the new ForgeOps release process

The new forgeops command is supported, so we’ve moved the corresponding documentation pages to the Reference section. Learn more in the forgeops command reference.

Considering the ForgeOps-provided docker images are supported, you need to build base Docker images only in special cases. Accordingly, we’ve moved the Base Docker Images section to the Reference section.