Question 1
When removing a forgeops deployment created with the Cloud Developer Kit (CDK) with the following command:
$ /path/to/forgeops/bin/forgeops delete
What components are removed from the deployment?
- AOption A:
The Ping Identity Platform (CDK artifacts, PVCs, and the Access Management and Identity Management configurations) and ingress controller pods
- BOption B:
The Ping Identity Platform (CDK artifacts, PVCs, and the Access Management and Identity Management configurations), certificate manager, and secret agent pods
- COption C:
The Ping Identity Platform (CDK artifacts, PVCs, and the Access Management and Identity Management configurations), ingress controller, DS operator, certificate manager, and secret agent pods
- DOption D:
The Ping Identity Platform (CDK artifacts, PVCs, and the Access Management and Identity Management configurations) pods
Show answer and explanation
Correct answer: D
The forgeops command-line tool is used to manage the lifecycle of the Ping Identity Platform in Kubernetes environments.9 When using the Cloud Developer Kit (CDK) for version 8.0.2, the delete subcommand is used to tear down the environment.
According to the "ForgeOps CLI Reference" and "CDK Shutdown and Removal" documentation:
The forgeops delete command (without additional flags like --force or specific component names) is designed to remove the Ping Identity Platform pods. This includes the core applications like PingAM, PingIDM, and PingDS, as well as the specialized UI pods (login-ui, etc.). It also removes the standard CDK artifacts and configuration manifests associated with that specific namespace.
However, the command follows a "safe delete" philosophy regarding infrastructure-level components:
Ingress Controllers, Certificate Managers (cert-manager), and the DS Operator are considered part of the "Base" or "Infrastructure" layer. These are typically installed once per cluster or namespace and are shared across multiple deployments. The forgeops delete command does not remove these by default, as doing so could disrupt other services.
PVCs (Persistent Volume Claims) and Secrets are also preserved unless the --force or -f flag is explicitly added to the command.
Thus, the answer is D . The command focuses strictly on the platform pods and their immediate deployment artifacts. If a developer wishes to perform a "deep clean" that removes the ingress and operators, they would need to use more specific commands like forgeops delete base or kubectl commands. 10 This distinction is vital for developers to avoid accidentally deleting shared cluster infrastructure when they only intended to restart the Ping platform.