What’s new in ForgeOps 2026.1
Release information
Highlights in 2026.1.0 release
ForgeOps team is testing and validating the 8.1.0 version of Ping Identity Platform products for deployment with ForgeOps. We’ll make the new images available for deployment as soon as possible. In the meantime, you can use the 8.0.x images for your ForgeOps deployment.
- Replaced ingress-nginx with Traefik as the default ingress controller
-
The default ingress controller has changed to Traefik because Kubernetes has retired the ingress-nginx controller. The ForgeOps documentation has been updated to reflect this change.
-
Learn more in the ForgeOps Architecture section.
-
Learn how to install Traefik in your cluster in the Prerequisites section.
-
- Configuration profiles built into their own images
-
The configuration profiles for AM and IDM have been separated into their own BusyBox images. You no longer need to build the AM and IDM Docker images for configuration changes.
The forgeops config command has a new
buildsubcommand to create custom BusyBox images for AM and IDM configuration profiles. ForgeOps deployment tools use the configuration images when available, and fall back to the built-in configuration in AM and IDM images.
To learn more, run the forgeops config build --help command.
- Update ForgeOps deployment environments
-
The new custom images require changes to your ForgeOps deployment environments. Update your default Kustomize overlay if you’re using the
FORGEOPS_DATAfunctionality. Run the forgeops env --env-name my-env --upgrade command in your environments to update the ForgeOps deployment environments to use the new configuration images. This command also updates the default Kustomize overlay when you run it the first time against any ForgeOps deployment environment.
More release information is available in the ForgeOps 2026.1 release notes.