Support for ForgeOps
This appendix contains information about support options for ForgeOps deployments and the Ping Identity Platform.
ForgeOps support
The Ping Identity ForgeOps team has developed artifacts in the forgeops and forgeops-extras Git repositories for deploying the Ping Identity Platform in the cloud. The companion ForgeOps documentation provides examples to help you get started.
These artifacts and documentation are provided on an as-is basis. Ping Identity doesn’t guarantee the individual success developers may have in implementing the code on their development platforms or in production configurations.
ForgeOps lifecycle policy
When a Ping Identity Platform software product has been deployed using ForgeOps, the product support lifecycle policy and timeline that applies to that product continues to apply regardless of the deployment type. These support policies relate to the Ping Identity Platform software product only and not the underlying container operating system. Therefore, refer to the support lifecycle policy for the relevant Ping Identity Platform product support lifecycle:
The support for the underlying container operating system is covered by the ForgeOps product support lifecycle policy.
ForgeOps product support lifecycle policy
ForgeOps product support lifecycle policy refers to the versions of the Ping Identity Platform software products that are supported by ForgeOps in ForgeOps version 2025.1 and later. ForgeOps will provide support for the last 3 minor or major versions of the Ping Identity Platform software products.
- Supported
-
ForgeOps will continue to deliver supported images for the latest available patch version of the platform product. For example, if versions 7.5.0 and 7.5.1 are available, ForgeOps provides scanned and patched images only for 7.5.1. These patched images deal with OS level vulnerabilities only and not the Ping Identity Platform software products.
- Maintained
-
ForgeOps tooling continues to have access to the last 4 versions of the Ping Identity Platform software products whether it’s supported or not.
Version Release Date Lifecycle Stage Supported? Maintained? EOS Start Date 8.0
Apr 7, 2025
Active
✅️
✅️
7.5
Apr 2, 2024
Active
✅
✅️
7.4
Oct 9, 2023
Active
✅
✅️
Licensing
Ping Identity only offers its software or services to legal entities that have entered into a binding license agreement with Ping Identity. When you install Docker images provided by ForgeOps, you agree either that: 1) you are an authorized user of a Ping Identity Platform customer that has entered into a license agreement with Ping Identity governing your use of the Ping Identity software; or 2) your use of the Ping Identity Platform software is subject to the Ping Identity Subscription Agreements.
Support
Ping Identity provides support for the following resources:
-
Docker images provided by the ForgeOps team.
-
Artifacts in the forgeops Git repository:
-
Files used to build Docker images for the Ping Identity Platform:
-
Dockerfiles
-
Scripts and configuration files incorporated into the Docker images provided by ForgeOps
-
Canonical configuration profiles for the platform
-
-
Helm charts
-
Kustomize bases and overlays
-
For more information about support for specific directories and files in the
forgeops repository, refer to the
forgeops repository reference.
Ping Identity provides support for the Ping Identity Platform. For supported components, containers, and Java versions, refer to the following:
Support limitations
Ping Identity provides no support for the following:
-
Artifacts in the forgeops-extras repository. For more information about support for specific directories and files in the
forgeops-extrasrepository, refer to theforgeops-extrasrepository reference. -
Artifacts other than Dockerfiles, Helm charts, Kustomize bases, and Kustomize overlays in the forgeops Git repository. Examples include scripts, example configurations, and so forth.
-
Infrastructure outside Ping Identity. Examples include Docker, Kubernetes, Google Cloud Platform, Amazon Web Services, Microsoft Azure, and so forth.
-
Software outside Ping Identity. Examples include Java, Apache Tomcat, NGINX, Apache HTTP Server, Certificate Manager, Prometheus, and so forth.
-
Deployments that deviate from the published ForgeOps architecture. Deployments that do not include the following architectural features are not supported:
-
PingAM and PingIDM are integrated and deployed together in a Kubernetes cluster.
-
PingIDM login is integrated with PingAM.
-
PingAM uses PingDS as its data repository.
-
PingIDM uses PingDS as its repository.
-
-
Ping Identity publishes Docker images for testing and development. For production deployments, it is recommended that customers build and run containers using a supported operating system, required software dependencies, and their customized platform component configurations.
Third-party Kubernetes services
The ForgeOps reference tools are provided for use with Google Kubernetes Engine, Amazon Elastic Kubernetes Service, and Microsoft Azure Kubernetes Service.
Ping Identity supports running the platform on other Kubernetes platforms such as IBM RedHat OpenShift. However, ForgeOps reference tools are not provided on these platforms, and customers must build, maintain, and support their own tools and configurations.
Ping Identity doesn’t support Kubernetes itself. Customers must have a support contract in place with their Kubernetes vendor to resolve infrastructure issues. To avoid any misunderstandings, it must be clear that Ping Identity cannot troubleshoot underlying Kubernetes issues.
Modifications to ForgeOps deployment assets may be required to adapt the platform to the customer’s Kubernetes implementation. For example, ingress routes, storage classes, NAT gateways, etc., might need to be modified. Making the modifications requires competency in Kubernetes and familiarity with their chosen distribution.
Documentation access
Ping Identity publishes comprehensive documentation online:
-
The Knowledge Base offers a large and increasing number of up-to-date, practical articles that help you deploy and manage Ping Identity Platform software.
While many articles are visible to community members, Ping Identity customers have access to much more, including advanced information for customers using Ping Identity Platform software in a mission-critical capacity.
-
The developer documentation, such as this site, aims to be technically accurate with respect to the sample that is documented. It is visible to everyone.
Problem reports and information requests
If you are a named customer Support Contact, contact Ping Identity using the
Customer Support Portal to request
information or report a problem with Dockerfiles, Helm charts, Kustomize bases,
or Kustomize overlays in the forgeops repository.
When requesting help with a problem, include the following information:
-
Description of the problem, including when the problem occurs and its impact on your operation.
-
Steps to reproduce the problem.
If the problem occurs on a Kubernetes system other than minikube, GKE, EKS, or AKS, we might ask you to reproduce the problem on one of those.
-
HTML output from the debug-logs command. For more information, refer to Kubernetes logs and other diagnostics.
Suggestions for fixes and enhancements to artifacts
ForgeOps greatly appreciates suggestions for fixes and enhancements to ForgeOps-provided artifacts in the forgeops and forgeops-extras repositories.
If you would like to report a problem with or make an enhancement request for an artifact in either repository, create a GitHub issue in the repository.
Contact information
Ping Identity provides support services, professional services, training through Ping Identity training, and partner services to assist you in setting up and maintaining your deployments. For a general overview of these services, refer to https://www.pingidentity.com/en/platform.html.
Ping Identity has staff members around the globe who support our international customers and partners. Learn more about Ping Identity’s support offering, including support plans and service-level agreements (SLAs) in the Ping Identity Platform support page.