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 and select ForgeOps 2025.1
Changes in the Documentation Digests section.
Or subscribe to the ForgeOps 2025.1 RSS feed.
Learn about how to configure GitHub notifications here so you can get notified on ForgeOps releases. |
Important information for this ForgeOps release:
Validated Kubernetes, NGINX Ingress Controller, HAProxy Ingress, cert-manager, and operator versions for deploying Ping Identity Platform 2025.1.1 |
|
Limitations when deploying Ping Identity Platform |
|
More information about the rapidly evolving nature of the |
|
Legal notices |
|
Archive of release notes in 2024 and before are available from ForgeOps release 7.5 documentation |
|
Archive of release notes in 2023 and before are available from ForgeOps release 7.4 documentation |
2025
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 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.
February 19, 2025
New ForgeOps 2025.1.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 aforgeops.conf
file in theirFORGEOPS_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 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 environmen. 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 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 Overview.
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. - 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
January 13, 2025
New features and updated functionality
- The ForgeOps releases are based on the
main
branch -
The
master
branch offorgeops
repository is no longer used. The ForgeOps artifacts are released from themain
branch. The latest Docker images are tagged asdev
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 command reference.
-
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 requiredldif-importer
scripts are mounted to theldif-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.
2024
December 05, 2024
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.