Architecture
This chapter covers all important aspects relating to the architecture of CPO and the associated components. In addition to the underlying Kubertnetes, the various components and their interaction for the operation of a PostgreSQL cluster are analysed.
![drawing](images/architecture_overview.png)
With internal PG cluster-internal traffic, we are talking about all traffic that is necessary for the operation of the cluster itself. This includes
- Communication for the sync of the replicas:
- pg_basebackup & streaming replication
- Communication with pgBackRest (if configured)
- Backups
- WAL archiving
- replica-create for new replicas
The figure below shows the internal traffic flows with pgBackRest based on block storage (left) or cloud storage (right)
![drawing](images/architecture_cluster_backup_pvc.png)
![drawing](images/architecture_cluster_backup_cloud_storage.png)
External traffic, i.e. the connection to the database for the user or the application, takes place via defined Kubernetes services. A distinction must be made here between read/write and read only traffic.