---
title: What’s new in ForgeOps 2026.1
description: ForgeOps team validated the 8.1.0 version of Ping Identity Platform products for deployment with ForgeOps. The following new secure images are available for ForgeOps deployment:
component: forgeops
version: 2026.1
page_id: forgeops:start:whats-new
canonical_url: https://docs.pingidentity.com/forgeops/2026.1/start/whats-new.html
section_ids:
  release_information: Release information
  update_in_2026_1_0_release: Update in 2026.1.0 release
  highlights_in_2026_1_release: Highlights in 2026.1 release
---

# What's new in ForgeOps 2026.1

## Release information

### Update in 2026.1.0 release

* The Ping Identity Platform version 8.1 product images are now available

  ForgeOps team validated the 8.1.0 version of Ping Identity Platform products for deployment with ForgeOps. The following new secure images are available for ForgeOps deployment:

  * AM 8.1.0

  * Amster 8.1.0

  * DS 8.1.0

  * IDM 8.1.0

Learn more on how to upgrade your deployed images in [upgrading deployed Docker images](../upgrade/upgrade-product.html).

### Highlights in 2026.1 release

* 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](../deploy/architecture.html#cdm-topology) section.

  * Learn how to install Traefik in your cluster in the [Prerequisites](../reference/forgeops-cmd-ref.html#prereqs-ref) section.

* Configuration profiles built into their own images

  The configuration profiles for AM and IDM have been separated into their own [BusyBox](# "A BusyBox container is a minimal, lightweight containerized environment that includes a compact implementation of common UNIX utilities.") images. You no longer need to build the AM and IDM Docker images for configuration changes.

  The forgeops config command has a new `build` subcommand to create custom [BusyBox](# "A BusyBox container is a minimal, lightweight containerized environment that includes a compact implementation of common UNIX utilities.") 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_DATA` functionality. 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](../rn/rn.html).