ForgeOps 2025.1 release notes | ForgeOps Documentation https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html ForgeOps 2025.1 release notes Tue, 06 Oct 2026 21:25:56 GMT https://validator.w3.org/feed/docs/rss2.html https://github.com/jpmonette/feed 5 Copyright 2026 Ping Identity. All rights reserved. <![CDATA[May 2026]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#may_2026 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#may_2026 Fri, 01 May 2026 21:00:00 GMT

Avoid using secret-agent versions 1.2.9 and 1.2.10

Versions 1.2.9 and 1.2.10 of secret-agent have a flaw that causes the secret-agent operator to crash when it tries to access the Kubernetes API. This issue is fixed in version 1.2.11 of secret-agent. If you are using versions 1.2.9 or 1.2.10, upgrade to version 1.2.11 or later to avoid this issue.

]]> <![CDATA[September 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#september_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#september_2025 Fri, 26 Sep 2025 21:00:00 GMT
Certificate expiry mitigation

In ForgeOps 2025.1 and earlier releases, the DS SSL key pairs were set up with an expiry of 3 years. This causes a failure of replication (ds-ssl-cert) and backup (ds-master-cert) certificates at restart. To work around this issue, you must delete the certificate object in Kubernetes and prevent automatic rotation of certificates:

kubectl delete certificate ds-master-cert ds-ssl-cert

This issue is fixed in ForgeOps 2025.2 release with the expiry of 30 years.

]]> <![CDATA[June 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#june_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#june_2025 Wed, 04 Jun 2025 21:00:00 GMT

Documentation updates

Added reference for secrets

Included a section to describe the different Kubernetes secrets used in ForgeOps. Learn more in Secrets Reference.

]]> <![CDATA[May 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#may_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#may_2025 Tue, 06 May 2025 21:00:00 GMT

Documentation updates

Workaround for AM base image creation

The script used for generating AM base image from AM zip file had a flaw. A workaround has been documented. Learn more in Base Docker images.

Updated Java version

Steps to build customized base images are updated to use Java version 21. Learn more at Base Docker images.

]]> <![CDATA[ForgeOps 2025.1.2 released]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#forgeops_2025_1_2_released https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#forgeops_2025_1_2_released Thu, 01 May 2025 21:00:00 GMT

New features and updated functionality

New PingGateway version available

PingGateway 2025.3.0 Docker image has been released. The forgeops command has been updated to deploy PingGateway in a ForgeOps deployment.

Updated PingGateway deployment to use the new admin endpoint

PingGateway has two endpoints now:

  • /ig the main entry point to PingGateway

  • /admin the API of the PingGateway administration, containing the /ping handler used for live check, for example.

Updated the Kubernetes version to 1.32

The Terraform cluster creation manifests have been updated to use Kubernetes version 1.32 on all platforms.

Custom environment variables in Helm chart

Implemented a mechanism to define extra environment variables for AM, IDM and custom variables to the platform configuration map.

Update the values.yaml file for your environments with the desired configuration. The env arrays should contain maps of Kubernetes environment configurations. The following sections in the charts/identity-platform/values.yaml file contain examples:

  • platform.configMap.data: Map of custom key,value pairs for platform-config

  • platform.env: Shared custom environment variables

  • am.env: AM custom environment variables

  • idm.env: IDM custom environment variables

The install-prereqs script is updated

The following new features have been added to the install-prereqs script:

  • A usage statement.

  • The --upgrade flag for easy upgrading of prereqs.

  • The ability to provide a config file to pin versions.

Prometheus and Grafana added to the Helm chart

Added the ability to enable Prometheus and Grafana in the Helm chart.

Improved release detection

Using forgeops image and forgeops info commands, you can now look for and select a newer version, skipping the version you specified in the command if it isn’t available.

Bugfixes

Fix --amster-retain option

Added the --amster-retain option to the forgeops env command. You can configure a ForgeOps deployment environment to keep the amster pod running for troubleshooting purposes.

Fix VolumeSnapshots in Kustomize deployments

The forgeops env command now adds a patch to update the namespace when enabling volume snapshots.

Removed Features

Removed the forgeops generate command

The deprecated forgeops generate command has been removed.

Removed the separate scripts to deploy certmanager and secret-agent

The certmanager-deploy.sh and secret-agent scripts have been removed in favor of the charts/scripts/install-prereqs script, which includes steps to deploy certmanager and secret-agent.

]]> <![CDATA[April 24, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_24_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_24_2025 Thu, 24 Apr 2025 23:23:59 GMT

ForgeOps updates

Platform product Docker images released

The following platform Docker images have been released:

PingAM

8.0.1

PingAM configuration upgrader

8.0.1

Amster

8.0.1

PingDS

8.0.0

PingIDM

8.0.0

PingGateway

2025.3.0

admin-ui

8.0.0

end-user-ui

8.0.0
]]> <![CDATA[April 22, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_22_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_22_2025 Tue, 22 Apr 2025 23:23:59 GMT

ForgeOps updates

The debug-logs utility updated

The debug-log utility is updated to use the new ForgeOps deployment environments and parameters. Learn more at Kubernetes logs and other diagnostics.

]]> <![CDATA[April 17, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_17_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_17_2025 Thu, 17 Apr 2025 23:23:59 GMT

ForgeOps updates

Updated Docker image for PingGateway

The Docker image for PingGateway is updated to 2025.3.0.

]]> <![CDATA[April 15, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_15_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_15_2025 Tue, 15 Apr 2025 23:23:59 GMT

Documentation update

Moved Ingress and Benchmark sections

Ingress and Benchmark sections are moved from the Prepare branch to the Reference navigation branch.

]]> <![CDATA[April 9, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_9_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_9_2025 Wed, 09 Apr 2025 23:23:59 GMT

Documentation updates

Third-party software

Updated the list of third-party software required for ForgeOps deployment. Included third-party software requirement in the Getting Started section. Learn more at your cluster environment at Setup overview.

ForgeOps updates

Prometheus update

Monitoring tools Grafana and Prometheus have been updated to use the latest versions, along with newer monitoring endpoints. Learn more at About ForgeOps deployment monitoring.

]]> <![CDATA[April 4, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_4_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#april_4_2025 Fri, 04 Apr 2025 23:23:59 GMT

Documentation updates

Removed the disaster subcommand from the ds-debug command

The DS team has removed the disaster subcommand from the ds-debug command. Accordingly, that subcommand description is removed from the Troubleshooting section.

Fixed the name of the ingress controller used

The name of the ingress controller used by default in ForgeOps deployment is corrected to Ingress-NGINX controller.

Corrected steps to install PingGateway

Procedures to install PingGateway are corrected. Learn more at Deploy PingGateway and Custom PingGateway image.

]]> <![CDATA[March 19, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#march_19_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#march_19_2025 Wed, 19 Mar 2025 23:23:59 GMT

Documentation updates

Revise steps to enable volume snapshots

The steps to enable volume snapshots have been simplified with the use of the forgeops env command. Learn more in Backup and restore using volume snapshots.

Command reference for forgeops image

Added the command reference for the forgeops image command. Learn more at the forgeops image command reference page.

]]> <![CDATA[March 05, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#march_05_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#march_05_2025 Wed, 05 Mar 2025 23:23:59 GMT

Documentation updates

Revamp the Upgrade section

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 and Migration Overview section.

Update the Troubleshooting amster section

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

]]> <![CDATA[February 19, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#february_19_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#february_19_2025 Wed, 19 Feb 2025 23:23:59 GMT

New ForgeOps 2025.1 released

New features and updated functionality

Ability to set FORGEOPS_ROOT

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 clone the forgeops repository and check out only the version tag you need. This makes it easier to keep track of the ForgeOps version you’re using and upgrade to a newer version consistently.

Don’t create or modify the forgeops.conf file in the /path/to/forgeops_repo/ directory.
forgeops info command can provide release information

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

You can get details for any release on releases.forgeops.com using the forgeops info --release xyz command.

forgeops env command supports PingGateway

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

Version of pyyaml is updated

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

Bugfixes

forgeops info --env-name command has been fixed

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

DS certificates are now deployed in Helm pre-install

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

AM service target ports are updated

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

Prometheus ports are updated

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

Documentation updates

Upgrade procedures revised

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

]]> <![CDATA[February 10, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#february_10_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#february_10_2025 Mon, 10 Feb 2025 23:23:59 GMT

New features and updated functionality

Added sample storage class definition files

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.

Documentation updates

Updated the procedure to set up Minikube cluster

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.

Updated the procedure to perform ForgeOps deployment on Minikube

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

]]> <![CDATA[January 27, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#january_27_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#january_27_2025 Mon, 27 Jan 2025 23:23:59 GMT

Documentation updates

Revised instruction for deployment on Minikube

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

Learn the revised steps to perform ForgeOps deployment on Minikube:

]]> <![CDATA[January 13, 2025]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#january_13_2025 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#january_13_2025 Mon, 13 Jan 2025 23:23:59 GMT

New features and updated functionality

The ForgeOps releases are based on the main branch

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.

New forgeops command

  • The forgeops-ng command has been renamed forgeops. The new forgeops command subsumes all the functionality provided by the previous version of forgeops command. The previous version of the forgeops-ng command has been removed.

  • The process of deploying and managing ForgeOps deployments has been improved with the use of provisioning environments with the forgeops env command for both Kustomize and Helm user environments. Learn more about the forgeops env command in the forgeops env command].

  • Provided an option to select the Docker image as appropriate for a user deployment with the forgeops image command.

  • You can view configured environments and product versions using the forgeops info command.

Learn more in forgeops command reference

ForgeOps-provided Docker images are now supported

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

New supported product versions

Platform UI

7.5.1

PingAM

7.4.1, 7.5.1

PingDS

7.4.3, 7.5.1

PingGateway

2024.6.0, 2024.9.0, 2024.11.0

PingIDM

7.5.0
Removed legacy DS docker directories

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.

Removed the requirement to build ldif-importer

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.

Documentation updates

New forgeops command reference

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

Description of the release process

Learn more about the new ForgeOps release process here

New section on customizing DS image

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

]]> <![CDATA[December 05, 2024]]> https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#december_05_2024 https://docs.pingidentity.com/forgeops/2025.1/rn/rn.html#december_05_2024 Thu, 05 Dec 2024 23:23:59 GMT

Documentation updates

Added description of the release process

Learn more about the new ForgeOps release process

Moved the forgeops command description and reference to the Reference section

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.

The previous version of the forgeops utility is not supported in this ForgeOps release. It continues to be supported in ForgeOps 7.5 and 7.4, as long as the corresponding Ping Identity Platform components are supported.
Moved Base Docker Image page to the Reference section

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.

]]>