delete-user

To delete a protected user partition, you must drop the associated Postgres schemas and trigger a portal deployment restart. This bypasses standard API restrictions to directly remove user-specific data footprints from the backend and clear cached in-memory nodes.

A deleted user may reappear in the portal because cached user nodes remain in memory. Orchestrating a portal deployment restart purges these cached nodes, ensuring the user cannot be resurrected by the system after their database schema is dropped.

The best way to clean up test user data in production AKS is to execute SQL commands against the internal Postgres database to drop user schemas, followed by restarting the portal deployment to purge any residual cached user nodes from the system.

Yes, you need kubectl access to the production AKS cluster and the ability to execute SQL commands against the internal Postgres database. These permissions are required to drop user partitions and trigger the necessary portal deployment restarts.

You should manually drop Postgres schemas when a user encounters a corrupted onboarding state or when you need to fully decommission a throwaway test account. This ensures no residual user-specific data remains in the backend database or portal memory.