--- title: ForgeOps 2025.1 release notes description: Get an email when there's an update to ForgeOps 2025.1 documentation. Go to the Notifications page in your Backstage profile and select ForgeOps 2025.1 Changes in the Documentation Digests section. component: forgeops version: 2025.1 page_id: forgeops:rn:rn canonical_url: https://docs.pingidentity.com/forgeops/2026.3/rn/rn.html llms_txt: https://docs.pingidentity.com/forgeops/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md superseded_by: https://docs.pingidentity.com/forgeops/2026.3/rn/rn.html section_ids: 2024: 2024 2025: 2025 2026: 2026 may_2026: May 2026 avoid_using_secret_agent_versions_1_2_9_and_1_2_10: Avoid using secret-agent versions 1.2.9 and 1.2.10 september_2025: September 2025 june_2025: June 2025 documentation_updates: Documentation updates may_2025: May 2025 documentation_updates_2: Documentation updates forgeops_2025_1_2_released: ForgeOps 2025.1.2 released new_features_and_updated_functionality: New features and updated functionality bugfixes: Bugfixes removed_features: Removed Features april_24_2025: April 24, 2025 forgeops_updates: ForgeOps updates april_22_2025: April 22, 2025 forgeops_updates_2: ForgeOps updates april_17_2025: April 17, 2025 forgeops_updates_3: ForgeOps updates april_15_2025: April 15, 2025 documentation_update: Documentation update april_9_2025: April 9, 2025 documentation_updates_3: Documentation updates forgeops_updates_4: ForgeOps updates april_4_2025: April 4, 2025 documentation_updates_4: Documentation updates march_19_2025: March 19, 2025 documentation_updates_5: Documentation updates march_05_2025: March 05, 2025 documentation_updates_6: Documentation updates february_19_2025: February 19, 2025 new_features_and_updated_functionality_2: New features and updated functionality bugfixes_2: Bugfixes documentation_updates_7: Documentation updates february_10_2025: February 10, 2025 new_features_and_updated_functionality_3: New features and updated functionality documentation_updates_8: Documentation updates january_27_2025: January 27, 2025 documentation_updates_9: Documentation updates january_13_2025: January 13, 2025 new_features_and_updated_functionality_4: New features and updated functionality documentation_updates_10: Documentation updates december_05_2024: December 05, 2024 documentation_updates_11: Documentation updates --- # ForgeOps `2025.1` release notes Get an email when there's an update to ForgeOps `2025.1` documentation. Go to the [Notifications page in your Backstage profile](https://backstage.forgerock.com/account/notifications/settings) and select ForgeOps `2025.1` Changes in the Documentation Digests section. Or subscribe to the [icon: rss-square, set=fa][ForgeOps 2025.1 RSS feed](https://docs.pingidentity.com/forgeops/2025.1/rn/rn.xml). | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | | Learn more about configuring GitHub notifications [here](https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications) so you can get notified on ForgeOps releases. | Important information for this ForgeOps release: | | | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | | Validated Kubernetes, Ingress-NGINX Controller, HAProxy Ingress, cert-manager, and operator versions for deploying Ping Identity Platform 2025.1.2 | [Link](versions.html) | | Limitations when deploying Ping Identity Platform `2025.1.2` on Kubernetes | [Link](limitations.html) | | More information about the rapidly evolving nature of the `forgeops` repository, including technology previews, legacy features, and feature deprecation and removal | [Link](evolution.html) | | Legal notices | [Link](legal.html) | | Archive of release notes in 2024 and before are available from ForgeOps release 7.5 documentation | [Link](https://docs.pingidentity.com/forgeops/7.5/rn/rn.html#2024) | | Archive of release notes in 2023 and before are available from ForgeOps release 7.4 documentation | [Link](https://docs.pingidentity.com/forgeops/7.4/rn/rn.html#2023) | ## 2026 ### May 2026 #### 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. ## 2025 ### September 2025 * 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. ### June 2025 #### Documentation updates * Added reference for secrets Included a section to describe the different Kubernetes secrets used in ForgeOps. Learn more in [Secrets Reference](../../2026.3/reference/secrets-reference.html). ### May 2025 #### 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](../../2026.3/reference/base-docker-images.html). * Updated Java version Steps to build customized base images are updated to use Java version 21. Learn more at [Base Docker images](../../2026.3/reference/base-docker-images.html). ### ForgeOps 2025.1.2 released #### 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`. ### April 24, 2025 #### 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** | ### April 22, 2025 #### 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](../../2026.3/troubleshoot/pods.html). ### April 17, 2025 #### ForgeOps updates * Updated Docker image for PingGateway The Docker image for PingGateway is updated to 2025.3.0. ### April 15, 2025 #### Documentation update * Moved Ingress and Benchmark sections Ingress and Benchmark sections are moved from the Prepare branch to the Reference navigation branch. ### April 9, 2025 #### 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](../../2026.3/setup/overview.html). #### 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](../../2026.3/prepare/monitoring/monitoring-intro.html). ### April 4, 2025 #### 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](../../2026.3/prepare/ig/deploy-default-ig.html) and [Custom PingGateway image](../../2026.3/prepare/ig/deploy-custom-ig.html). ### March 19, 2025 #### 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](../../2026.3/backup/snapshots.html). * Command reference for forgeops image Added the command reference for the forgeops image command. Learn more at the [forgeops image command reference page](../../2026.3/reference/forgeops-cmd-ref.html#forgeops-image). ### March 05, 2025 #### 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](../../2026.3/upgrade/upgrade-overview.html) section. * Update the Troubleshooting `amster` section The amster command has been subsumed in the forgeops amster command. Learn more in the [Troubleshooting `amster` pod](../../2026.3/troubleshoot/amster.html) section. ### February 19, 2025 **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](../../2026.3/upgrade/upgrade-overview.html). ### February 10, 2025 #### 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](../../2026.3/setup/minikube.html). * 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. ### January 27, 2025 #### 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: * [Using Helm](../deploy/deploy-scenario-helm-local.html). * [Using Kustomize](../deploy/deploy-scenario-kustomize-local.html). ### January 13, 2025 #### 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](../../2026.3/reference/forgeops-cmd-ref.html#env-ref)]. * 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](../../2026.3/reference/forgeops-cmd-ref.html) * 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](../../2026.3/reference/forgeops-cmd-ref.html) contains more information on the new forgeops command. * Description of the release process Learn more about the new ForgeOps release process [here](../../2026.3/start/release-process.html) * New section on customizing DS image Learn more about customizing DS image in the new section on [Customizing DS image](../../2026.3/customize/ds.html). ## 2024 ### December 05, 2024 #### Documentation updates * Added description of the release process Learn more about [the new ForgeOps release process](../../2026.3/start/release-process.html) * 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](../reference/forgeops.html). | | | | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | 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](../../2026.3/reference/base-docker-images.html) section to the Reference section.