Shutting down the Postgres database in the Management subsystem on different environments
Shut down or fence the Postgres database in the Management subsystem to prevent data corruption, ensure safe failover, or perform maintenance tasks across development, staging, and production environments.
Before you begin
- Make sure that the EDB cluster is healthy and running.
- If the EDB cluster shuts down due to an issue in any environment, such as full disks, resolve the issue and then restart the cluster.
About this task
The shutdown of the Postgres database is controlled using the
k8s.enterprisedb.io/fencedInstances
annotation, which accepts a JSON-formatted list
of instance names. If the annotation is set to ["*"]
, a singleton list with a
wildcard, the entire cluster is shut down. To shut down only one EDB instance, replace the
"*"
in the command with the instance name.
Note: The OVA package includes API Connect with the CNP plug-in
preinstalled. To install the CNP plug-in for other environments, see https://github.com/EnterpriseDB/kubectl-cnp.