Uninstall Keycloak
Keycloak is installed as part of the Virtana Platform to provide single sign-on (SSO) and token-based authentication for GlobalView, Container Observability (CO), and other platform components. Uninstalling it revokes the authentication layer shared by these components, so ensure all dependent services have been removed or reconfigured before proceeding.
Caution
Keycloak acts as the central authentication provider for the Virtana Platform. Removing it before uninstalling GlobalView or Container Observability will cause those components to lose authentication capability. Uninstall Keycloak last, after all dependent platform components have been removed.
If your Helm release was previously named opscruise-keycloak (used in older deployments), substitute that name for virtana-keycloak in the command below.
Remove the Keycloak Helm release
Run the following command to uninstall the Virtana Keycloak Helm release. This removes all Kubernetes resources created by the chart, including deployments, services, config maps, and secrets managed by Helm, from the keycloak namespace.
helm uninstall virtana-keycloak -n keycloak
After the command completes, verify that all Keycloak pods have terminated by running:
kubectl get pods -n keycloak
The namespace should return no running pods. Any resources that remain are those not managed by Helm (such as manually created PVCs or secrets) and must be removed separately if you want a clean namespace.
Delete the Keycloak namespace (optional)
If you want to remove all remaining resources, including any PVCs, secrets, and config maps not managed by Helm, delete the namespace itself. This step is irreversible and removes all persistent data associated with Keycloak, including the embedded PostgreSQL database that stores realm, user, and client configuration.
kubectl delete namespace keycloak
Note
Skip this step if you plan to reinstall Keycloak later and want to retain existing realm data.