--- title: ForgeOps 7.5 release notes description: Subscribe to the ForgeOps 7.5 RSS feed. component: forgeops version: 7.5 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 automatic_email_notification_is_discontinued: Automatic email notification is discontinued forgeops_release_release7_5_20251119: ForgeOps Release release/7.5-20251119 november_12_2025: November 12, 2025 deprecation: Deprecation august_7_2025: August 7, 2025 documentation_update: Documentation update july_15_2025: July 15, 2025 documentation_update_2: Documentation update march_29_2025: March 29, 2025 documentation_update_3: Documentation update november_20_2024: November 20, 2024 documentation_updates: Documentation updates november_6_2024: November 6, 2024 documentation_updates_2: Documentation updates september_6_2024: September 6, 2024 documentation_updates_3: Documentation updates august_14_2024: August 14, 2024 changes: Changes july_12_2024: July 12, 2024 documentation_updates_4: Documentation updates july_2_2024: July 2, 2024 june_20_2024: June 20, 2024 highlights: Highlights june_10_2024: June 10, 2024 documentation_updates_5: Documentation updates may_28_2024: May 28, 2024 documentation_updates_6: Documentation updates may_13_2024: May 13, 2024 changes_2: Changes may_09_2024: May 09, 2024 documentation_updates_7: Documentation updates april_17_2024: April 17, 2024 documentation_updates_8: Documentation updates april_3_2024: April 3, 2024 highlights_2: Highlights changes_3: Changes documentation_updates_9: Documentation updates --- # ForgeOps 7.5 release notes Subscribe to the [icon: rss-square, set=fa][ForgeOps 7.5 RSS feed](https://docs.pingidentity.com/forgeops/7.5/rn/rn.xml). Important information for this ForgeOps release: | | | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ | | Validated Kubernetes, Ingress-NGINX Controller, HAProxy Ingress, cert-manager, and operator versions for deploying Ping Identity Platform 7.5 | [Link](versions.html) | | Limitations when deploying Ping Identity Platform 7.5 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 prior to October 13, 2023 | [Link](archive/rn.html) | ## 2026 ### Automatic email notification is discontinued Because the documentation hosting has moved from Backstage, the automated email notification of ForgeOps documentation release changes is no longer available. Customers can subscribe to the [ForgeOps 7.5 RSS feed](https://docs.pingidentity.com/forgeops/7.5/rn/rn.xml). ## 2025 ### ForgeOps Release release/7.5-20251119 New ForgeOps release release/7.5-20251119 has been released. This release contains the newly released Ping Identity Platform products: * DS version 7.5.3 * AM and Amster version 7.5.2 * IDM version 7.5.2 * PingGateway version 2025.9 ### November 12, 2025 #### Deprecation * Deprecation of `vars` in Kustomize The `vars` feature used by ForgeOps before release 2025.1.0 has been deprecated in Kustomize. The `vars` feature is unavailable in newer versions of Kustomize. Kustomize doesn't provide ways to migrate `vars`. So we recommend customers to migrate to the ForgeOps release 2025.1.0 or later at their earliest possibility to avoid errors during ForgeOps deployment. ### August 7, 2025 #### Documentation update Revised the third-party software requirements table. ### July 15, 2025 #### Documentation update * `forgeops-minikube` command deprecated Python Software Foundation doesn't support PyYaml any longer, and the PyYaml package is removed from Homebrew. The steps to set up minikube clusters have been updated to replace the `forgeops-minikube` command. Learn more in [minikube cluster](../../2026.3/setup/minikube.html#minikube-cluster). ### March 29, 2025 #### Documentation update * Ingress controller name updated Revised the name of the ingress controller used in the default ForgeOps deployment to Ingress-NGINX controller. ## 2024 ### November 20, 2024 #### Documentation updates * ForgeOps-provided Docker images are now supported Ping Identity now supports ForgeOps-provided evaluation Docker images. Accordingly, the documentation is revised, and the "unsupported" admonition is removed. ### November 6, 2024 #### Documentation updates * Procedure to build `ldif-importer` Docker image We've added steps to build `ldif-importer` Docker image. Learn more about building ldif-importer Docker image [here](../prepare/base-docker-images.html#buid-ldif-imp). ### September 6, 2024 #### Documentation updates * New section on customizing DS image We've added a section on customizing DS image. Learn more about customizing DS image [here](../customize/ds.html). ### August 14, 2024 #### Changes * Enable setting TLS certificate issuer Added the ability to set a TLS certificate issuer. * Updated the platform UI versions Updated the platform UI versions to 7.5.1. * Updated Kubernetes version The ForgeOps deployment has been tested with Kubernetes version 1.30. ### July 12, 2024 #### Documentation updates * Added Bash version 4 or above to the required third-party software Bash version 4 or above is required to run `mapfile` used by the snapshot-restore.sh and stdlib.sh scripts. snapshot-restore.sh is used when restoring DS from snapshot backup. stdlib.sh contains general functions that are used by other Bash scripts. ### July 2, 2024 * Updates to the required third-party software The required third-party software table has been updated. ### June 20, 2024 #### Highlights * New Docker images for UI components are now available New Docker image versions are now available for the following components: * `platform-admin-ui` * `platform-enduser-ui` * `platform-login-ui` The documentation has been updated to refer to these new versions of Docker images. ### June 10, 2024 #### Documentation updates * Podman support in forgeops command Documented Podman container engine support in \`forgeops-ng build command. ### May 28, 2024 #### Documentation updates * Technology preview with the forgeops-ng command Added a new technology preview section with the description of the forgeops-ng command. Refer to [the `forgeops-ng` command](../tech-preview/forgeops-ng.html) for further information. ### May 13, 2024 #### Changes * Updated `ds-operator` to version 0.3.0 The DS Operator is updated to version v0.3.0 with security updates. Refer to the [DS operator release notes](https://github.com/ForgeRock/ds-operator/blob/v0.3.0/README.md) for full details. ### May 09, 2024 #### Documentation updates * Backup and restore steps in Helm-based deployments Added steps to set up and customize backup using volume snapshot backup in Helm-based deployments. Also added steps to restore from backup taken with dsbackup utility in Helm-based deployments. Refer to [Backup and restore using volume snapshots](../backup/snapshots.html) and [dsbackup utility](../backup/dsbackup.html). * References to articles on logging Added links to AM and IDM logging articles in the Troubleshooting page. ### April 17, 2024 #### Documentation updates * Link to DS scripts Added a link to [community articles on DS scripts](https://community.forgerock.com/t/forgeops-ds-script-guide-7-4-7-5/5522). ### April 3, 2024 #### Highlights * Updates to the `forgeops` repository Updates for Ping Identity Platform version 7.5 are available in the `release/7.5-20251119` branch of the `forgeops` repository. * Terminology change: removal of the terms CDK and CDM The ForgeOps documentation has been revised to no longer use the terms CDK and CDM. Deployments based on `forgeops` repository artifacts are now referred to simply as *ForgeOps deployments*. When they were initially developed, there were significant difference between the CDK and CDM deployments. This is no longer the case. Because of this, the documentation now uses a single name for all deployments. Developers who configure AM and IDM are still required to use ForgeOps deployments that have single instances of AM and IDM. This type of ForgeOps deployment is now referred to in documentation as a *single-instance ForgeOps deployment*. For more information, refer to [Cluster and deployment sizes](../deploy/architecture.html#cluster-and-deployment-sizes) on the [ForgeOps architecture](../deploy/architecture.html) page. * Perform ForgeOps deployments using Helm In version 7.5, you can perform ForgeOps deployments using Helm. Helm deployments are available as an alternative to using the forgeops install command, which uses Kustomize bases and overlays. Performing ForgeOps deployments with the forgeops install command continues to be supported. For more information and example commands, refer to the following pages: * [Perform a ForgeOps deployment using Helm on GKE, EKS, or AKS](../deploy/deploy-scenario-helm-cloud.html) * [Perform a ForgeOps deployment using Helm on minikube](../deploy/deploy-scenario-helm-local.html) * [Remove a ForgeOps Helm deployment from GKE, EKS, or AKS](../deploy/remove.html#helm-cloud) * [Remove a ForgeOps Helm deployment from minikube](../deploy/remove.html#helm-local) If you perform ForgeOps deployments with Helm, you'll still need to use the forgeops command for several use cases: * forgeops build to build custom Docker images * forgeops info to write administrative passwords and URLs for accessing Ping Identity Platform admin UIs to standard output Helm deployment does not support Kustomize manifest generation using the forgeops generate command. Continue deploying the platform with the forgeops command if you use Kustomize manifest generation. Existing Kustomize-based deployments can't be changed to be Helm-based. If you want to use Helm, create a new deployment separate from any existing Kustomize-based deployments. * forgeops-minikube command replaces cdk-minikube The forgeops-minikube command is used for setting up a minikube cluster locally instead of cdk-minikube. The forgeops-minikube command requires the `PyYaml` Python 3 package. #### Changes * Updated `ds-operator` to version 0.2.9 The DS Operator is updated to version v0.2.9 with security updates and patches, and to fix a bug that prevented kubectl rollout restart from working properly. Refer to the [DS operator release notes](https://github.com/ForgeRock/ds-operator/releases/tag/v0.2.9) for full details. This is the new minimum `ds-operator` version supported by the forgeops command. * Support for annotations and labels in the `directoryservice` custom resource The `directoryservice` custom resource now supports annotations and labels. #### Documentation updates * New layout of documentation The layout of the ForgeOps documentation has been revised to make it easier to navigate through the documentation and search for topics of interest. * Updated the steps to build custom IDM base image The procedure to build custom IDM base image has been revised. Refer to the [steps to build IDM base image](../prepare/base-docker-images.html#idm-base-image) for more information. * New backup and restore procedures using volume snapshots A new [Backup and restore using volume snapshots](../backup/snapshots.html) section has been added which describes how to use Kubernetes volume snapshots to back up and restore DS data. * Docker images for Helm installs Instructions about how to specify Docker images for Helm installs have been added. * New task to initialize deployment environments A [new task](../customize/setup.html#deploy-env-init) to initialize deployment environments has been added to the instructions for developing custom Docker images. Before you can use a new deployment environment, you must initialize a directory that supports the environment. * Clarification about support for environments that deviate from the published ForgeOps architecture The [Support for ForgeOps](../start/support.html) page has been updated to state that environments that deviate from the published ForgeOps architecture are not supported. For details, refer to [Support limitations](../start/support.html#support-limitations).