The forgeops delete command is designed to remove the specific Ping Identity Platform deployment created by the Cloud Developer Kit (CDK). This includes the Kubernetes resources that constitute the platform stack, such as the pods, services, and deployments for Access Management, Identity Management, and Directory Services. It also removes the associated Persistent Volume Claims (PVCs) and configuration artifacts. The command's scope is intentionally limited to the application stack itself and does not remove shared, cluster-level prerequisites.

A. The ingress controller is a cluster-level prerequisite and is not removed by the forgeops delete command.

B. The certificate manager and secret agent are cluster-level prerequisites and are not removed by the forgeops delete command.

C. The ingress controller, DS operator, certificate manager, and secret agent are all cluster-level prerequisites not managed by the CDK deployment lifecycle.

1. Ping Identity DevOps Documentation, forgeops > Get started > Clean up your CDK deployment. The documentation states: "When you're finished with your CDK deployment, run the forgeops delete command. This command deletes the Ping Identity Platform deployment and the persistent volume claims from your Kubernetes cluster." It makes no mention of removing cluster prerequisites like ingress or cert-manager.