![]() The Kubernetes PersistentVolumeClaim access modes for the PostgreSQL Tablespaces storage The Kubernetes PersistentVolumeClaim size for the PostgreSQL Tablespaces storage The tablespaceStorages section in the deploy/cr.yamlįile contains configuration options for PostgreSQL Tablespace. Name of the Custom configuration options ConfigMap for PostgreSQL cluster The Kubernetes annotations metadata for pgPrimary The range of client IP addresses from which the load balancer should be reachable (if not set, there is no limitations) The static IP-address for the load balancer Specifies the type of Kubernetes Service for pgPrimary Optionally sets the Kubernetes storage class to use with the PostgreSQL Primary storage PersistentVolumeClaimĪ PostgreSQL Primary storage label selector using hostpath) or dynamic (for a dynamic storage provisioner, e.g. Type of the PostgreSQL Primary storage provisioning: create (the default variant used if storage is provisioned, e.g. The Kubernetes PersistentVolumeClaim access modes for the PostgreSQL Primary storage The Kubernetes PersistentVolumeClaim size for the PostgreSQL Primary storage Set labels for PostgreSQL instances Node affinityĪllows using standard Kubernetes affinity constraints for advanced affinity and anti-affinity tuning Node affinity type, can be either preferred or required Pod anti-affinity type, can be either preferred or required The Kubernetes memory limits for a PostgreSQL Primary container Kubernetes CPU limits for a PostgreSQL Primary container Kubernetes CPU requests for a PostgreSQL Primary container The Kubernetes memory requests for a PostgreSQL Primary container ![]() This option is used to set the policy for updating pgPrimary and pgReplicas images The Docker image of the PostgreSQL Primary instance Perconalab/percona-postgresql-operator:main-ppg13-postgres-ha The pgPrimary section controls the PostgreSQL Primary instance. Scheduled time to check for updates, specified in the crontab format Never or Disabled will completely disable automatic upgrades, otherwise it can be set to Latest or Recommended or to a specific version number of Percona Distribution for PostgreSQL to have it version-locked (so that the user can control the version running, but use automatic upgrades to move between them). Specifies how updates are processed by the Operator. The Version Service URL used to check versions compatibility for upgrade The upgradeOptions section in the deploy/cr.yaml file contains various configuration options to control Percona Distribution for PostgreSQL upgrades. The name of a data source PostgreSQL cluster, which is used to restore backup to a new clusterĬustom pgBackRest options to restore backup to a new cluster If true, local backups will be kept after the cluster deletion If true, PVCs will be kept after the cluster deletion The name of the secret created to encrypt internal communications The name of the secret created to encrypt external communications The name of the secret created to store credentials for system users The name of the secret with TLS used for both connection encryption (external traffic), and replication (internal traffic) By default, every cluster can have high availability if there is at least one replicaĮnforece Operator to use only Transport Layer Security (TLS) for both internal and external communications The name of a database that the PostgreSQL user can log into after the PostgreSQL cluster is created The pgBadger PostgreSQL log analyzer section Section required to manage the replicas within a PostgreSQL cluster Percona Monitoring and Management section Section to configure backups and pgBackRest PostgreSQL Primary instance options section Percona Distribution for PostgreSQL upgrade options section Pause/resume: setting it to true gracefully stops the cluster, and setting it to false after shut down starts the cluster back. The spec part of the deploy/cr.yaml file contains the following sections: Key name ( cluster1 by default) sets the name of your Percona Distributionįor PostgreSQL Cluster it should include only URL-compatible characters, not exceed 22 characters, start with an alphabetic character, and end with an alphanumeric character.The metadata part of this file contains the following keys: Use PostgreSQL tablespaces with Percona Operator for PostgreSQLĬreating a private S3-compatible cloud for backups Provide Percona Operator for PostgreSQL single-namespace and multi-namespace deployment Monitor with Percona Monitoring and Management (PMM)ĭeploy a standby cluster for Disaster Recovery Upgrade Percona Distribution for PostgreSQL and the Operator Install on Google Kubernetes Engine (GKE)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |