华为云kubernetes部署pg数据库一主两从

最新推荐文章于 2025-03-19 16:04:16 发布
最新推荐文章于 2025-03-19 16:04:16 发布
阅读量198 收藏 2
点赞数 4
分类专栏： kubernetes 文章标签： kubernetes 数据库 pg postgresql
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/nangonghen/article/details/146056495
版权

1 概述

部署pg数据库一主两从，pg版本是v 15.10.0，参考bitnami/postgresql-ha。

2 环境准备

2.1 购买SFS Turbo实例

在这里插入图片描述

2.2 购买华为云容器集群CCE实例

在这里插入图片描述

2.3 在k8s中创建storageclass对象

参数everest.io/share-access-to是VPC的ID。
参数everest.io/share-export-location是sfs turbo实例的共享路径:自定义子目录，sfs turbo实例的共享路径是在sfs实例的详细页查询，自定义子目录可以是任意路径。
参数everest.io/volume-id是sfs turbo实例的ID。
只需要修改以上三个参数。

在本文，storageclass的名称叫做sfsturbo-subpath-sc。

apiVersion: storage.k8s.io/v1
allowVolumeExpansion: true
kind: StorageClass
metadata:
  name: sfsturbo-subpath-sc
mountOptions:
- lock
parameters:
  csi.storage.k8s.io/csi-driver-name: sfsturbo.csi.everest.io
  csi.storage.k8s.io/fstype: nfs
  everest.io/archive-on-delete: "true"
  everest.io/share-access-to: xxxxxxxxxxxxxxxxxx   # VPC ID
  everest.io/share-expand-type: bandwidth
  everest.io/share-export-location: xxxxx.sfsturbo.internal:/mydir   # sfs turbo实例的共享路径:自定义子目录
  everest.io/share-source: sfs-turbo
  everest.io/share-volume-type: STANDARD
  everest.io/volume-as: subpath
  everest.io/volume-id: xxxxxxxxxxxxx   # sfs turbo实例的ID
provisioner: everest-csi-provisioner
reclaimPolicy: Retain
volumeBindingMode: Immediate

3 部署

直接apply下面的文件即可，所用的storageclass名称是刚刚创建的sfsturbo-subpath-sc。
账号是postgres，密码是ilovepg@2025。

---
# Source: postgresql-ha/templates/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: pg-postgresql-ha
  namespace: "default"
  labels:
    app.kubernetes.io/instance: pg
automountServiceAccountToken: false
---
# Source: postgresql-ha/templates/pgpool/secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: pg-postgresql-ha-pgpool
  namespace: "default"
  labels:
    app.kubernetes.io/instance: pg
type: Opaque
data:
  admin-password: "VlJrTzV1ajBBSg=="
---
# Source: postgresql-ha/templates/postgresql/secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: pg-postgresql-ha-postgresql
  namespace: "default"
  labels:
    app.kubernetes.io/instance: pg
type: Opaque
data:
  password: "aWxvdmVwZ0AyMDI1"
  repmgr-password: "aEticEpxRmJpMQ=="
---
# Source: postgresql-ha/templates/postgresql/hooks-scripts-configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: pg-postgresql-ha-postgresql-hooks-scripts
  namespace: "default"
  labels:
    app.kubernetes.io/instance: pg
data:
  pre-stop.sh: |-
    #!/bin/bash
    set -o errexit
    set -o pipefail
    set -o nounset

    # Debug section
    exec 3>&1
    exec 4>&2

    # Process input parameters
    MIN_DELAY_AFTER_PG_STOP_SECONDS=$1

    # Load Libraries
    . /opt/bitnami/scripts/liblog.sh
    . /opt/bitnami/scripts/libpostgresql.sh
    . /opt/bitnami/scripts/librepmgr.sh

    # Load PostgreSQL & repmgr environment variables
    . /opt/bitnami/scripts/postgresql-env.sh

    # Auxiliary functions
    is_new_primary_ready() {
        return_value=1
        currenty_primary_node="$(repmgr_get_primary_node)"
        currenty_primary_host="$(echo $currenty_primary_node | awk '{print $1}')"

        info "$currenty_primary_host != $REPMGR_NODE_NETWORK_NAME"
        if [[ $(echo $currenty_primary_node | wc -w) -eq 2 ]] && [[ "$currenty_primary_host" != "$REPMGR_NODE_NETWORK_NAME" ]]; then
            info "New primary detected, leaving the cluster..."
            return_value=0
        else
            info "Waiting for a new primary to be available..."
        fi
        return $return_value
    }

    export MODULE="pre-stop-hook"

    if [[ "${BITNAMI_DEBUG}" == "true" ]]; then
        info "Bash debug is on"
    else
        info "Bash debug is off"
        exec 1>/dev/null
        exec 2>/dev/null
    fi

    postgresql_enable_nss_wrapper

    # Prepare env vars for managing roles
    readarray -t primary_node < <(repmgr_get_upstream_node)
    primary_host="${primary_node[0]}"

    # Stop postgresql for graceful exit.
    PG_STOP_TIME=$EPOCHSECONDS
    postgresql_stop

    if [[ -z "$primary_host" ]] || [[ "$primary_host" == "$REPMGR_NODE_NETWORK_NAME" ]]; then
        info "Primary node need to wait for a new primary node before leaving the cluster"
        retry_while is_new_primary_ready 10 5
    else
        info "Standby node doesn't need to wait for a new primary switchover. Leaving the cluster"
    fi

    # Make sure pre-stop hook waits at least 25 seconds after stop of PG to make sure PGPOOL detects node is down.
    # default terminationGracePeriodSeconds=30 seconds
    PG_STOP_DURATION=$(($EPOCHSECONDS - $PG_STOP_TIME))
    if (( $PG_STOP_DURATION < $MIN_DELAY_AFTER_PG_STOP_SECONDS )); then
        WAIT_TO_PG_POOL_TIME=$(($MIN_DELAY_AFTER_PG_STOP_SECONDS - $PG_STOP_DURATION)) 
        info "PG stopped including primary switchover in $PG_STOP_DURATION. Waiting additional $WAIT_TO_PG_POOL_TIME seconds for PG pool"
        sleep $WAIT_TO_PG_POOL_TIME
    fi

  readiness-probe.sh: |-
    #!/bin/bash
    set -o errexit
    set -o pipefail
    set -o nounset

    # Debug section
    exec 3>&1
    exec 4>&2

    # Load Libraries
    . /opt/bitnami/scripts/liblog.sh
    . /opt/bitnami/scripts/libpostgresql.sh

    # Load PostgreSQL & repmgr environment variables
    . /opt/bitnami/scripts/postgresql-env.sh

    # Process input parameters
    MIN_DELAY_AFTER_POD_READY_FIRST_TIME=$1
    TMP_FIRST_READY_FILE_TS="/tmp/ts-first-ready.mark"
    TMP_DELAY_APPLIED_FILE="/tmp/delay-applied.mark"

    DB_CHECK_RESULT=$(echo "SELECT 1" | postgresql_execute_print_output "$POSTGRESQL_DATABASE" "$POSTGRESQL_USERNAME" "$POSTGRESQL_PASSWORD" "-h 127.0.0.1 -tA" || echo "command failed")
    if [[ "$DB_CHECK_RESULT" == "1" ]]; then
      if [[ ! -f "$TMP_DELAY_APPLIED_FILE" ]]; then
        # DB up, but initial readiness delay not applied
        if [[ -f "$TMP_FIRST_READY_FILE_TS" ]]; then
          # calculate delay from the first readiness success
          FIRST_READY_TS=$(cat $TMP_FIRST_READY_FILE_TS)
          CURRENT_DELAY_SECONDS=$(($EPOCHSECONDS - $FIRST_READY_TS))
          if (( $CURRENT_DELAY_SECONDS > $MIN_DELAY_AFTER_POD_READY_FIRST_TIME )); then
            # minimal delay of the first readiness state passed - report success and mark delay as applied
            touch "$TMP_DELAY_APPLIED_FILE"
          else
            # minimal delay of the first readiness state not reached yet - report failure
            exit 1
          fi
        else
          # first ever readiness test success - store timestamp and report failure
          echo $EPOCHSECONDS > $TMP_FIRST_READY_FILE_TS
          exit 1
        fi
      fi
    else
      # DB test failed - report failure
      exit 1
    fi
---
# Source: postgresql-ha/templates/pgpool/service.yaml
apiVersion: v1
kind: Service
metadata:
  name: pg-postgresql-ha-pgpool
  namespace: "default"
  labels:
    app.kubernetes.io/instance: pg
spec:
  type: ClusterIP
  sessionAffinity: None
  ports:
    - name: "postgresql"
      port: 5432
      targetPort: postgresql
      protocol: TCP
      nodePort: null
  selector:
    app.kubernetes.io/instance: pg
    app.kubernetes.io/component: pgpool
---
# Source: postgresql-ha/templates/postgresql/service-headless.yaml
apiVersion: v1
kind: Service
metadata:
  name: pg-postgresql-ha-postgresql-headless
  namespace: "default"
  labels:
    app.kubernetes.io/instance: pg
spec:
  type: ClusterIP
  clusterIP: None
  publishNotReadyAddresses: false
  ports:
    - name: "postgresql"
      port: 5432
      targetPort: postgresql
      protocol: TCP
  selector:
    app.kubernetes.io/instance: pg
    app.kubernetes.io/component: postgresql
    role: data
---
# Source: postgresql-ha/templates/postgresql/service.yaml
apiVersion: v1
kind: Service
metadata:
  name: pg-postgresql-ha-postgresql
  namespace: "default"
  labels:
    app.kubernetes.io/instance: pg
spec:
  type: ClusterIP
  ports:
    - name: "postgresql"
      port: 5432
      targetPort: postgresql
      protocol: TCP
  selector:
    app.kubernetes.io/instance: pg
    role: data
---
# Source: postgresql-ha/templates/pgpool/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: pg-postgresql-ha-pgpool
  namespace: "default"
  labels:
    app.kubernetes.io/instance: pg
    app.kubernetes.io/component: pgpool
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/instance: pg
      app.kubernetes.io/component: pgpool
  template:
    metadata:
      labels:
        app.kubernetes.io/instance: pg
        app.kubernetes.io/component: pgpool
    spec:
      
      automountServiceAccountToken: false
      affinity:
        podAffinity:
          
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
            - podAffinityTerm:
                labelSelector:
                  matchLabels:
                    app.kubernetes.io/instance: pg
                    app.kubernetes.io/component: pgpool
                topologyKey: kubernetes.io/hostname
              weight: 1
        nodeAffinity:
          
      securityContext:
        fsGroup: 1001
        fsGroupChangePolicy: Always
        supplementalGroups: []
        sysctls: []
      serviceAccountName: pg-postgresql-ha
      # Auxiliary vars to populate environment variables
      containers:
        - name: pgpool
          image: docker.io/bitnami/pgpool:4.6.0-debian-12-r0
          imagePullPolicy: "IfNotPresent"
          securityContext:
            allowPrivilegeEscalation: false
            capabilities:
              drop:
              - ALL
            privileged: false
            readOnlyRootFilesystem: true
            runAsGroup: 1001
            runAsNonRoot: true
            runAsUser: 1001
            seLinuxOptions: {}
            seccompProfile:
              type: RuntimeDefault
          env:
            - name: BITNAMI_DEBUG
              value: "false"
            - name: PGPOOL_BACKEND_NODES
              value: 0:pg-postgresql-ha-postgresql-0.pg-postgresql-ha-postgresql-headless:5432,1:pg-postgresql-ha-postgresql-1.pg-postgresql-ha-postgresql-headless:5432,2:pg-postgresql-ha-postgresql-2.pg-postgresql-ha-postgresql-headless:5432,
            - name: PGPOOL_SR_CHECK_USER
              value: "repmgr"
            - name: PGPOOL_SR_CHECK_PASSWORD_FILE
              value: "/opt/bitnami/pgpool/secrets/pgpool-sr-check-password"
            - name: PGPOOL_SR_CHECK_DATABASE
              value: "postgres"
            - name: PGPOOL_ENABLE_LDAP
              value: "no"
            - name: PGPOOL_POSTGRES_USERNAME
              value: "postgres"
            - name: PGPOOL_POSTGRES_PASSWORD_FILE
              value: "/opt/bitnami/pgpool/secrets/pgpool-password"
            - name: PGPOOL_ADMIN_USERNAME
              value: "admin"
            - name: PGPOOL_ADMIN_PASSWORD_FILE
              value: "/opt/bitnami/pgpool/secrets/admin-password"
            - name: PGPOOL_AUTHENTICATION_METHOD
              value: "scram-sha-256"
            - name: PGPOOL_ENABLE_LOAD_BALANCING
              value: "yes"
            - name: PGPOOL_DISABLE_LOAD_BALANCE_ON_WRITE
              value: "transaction"
            - name: PGPOOL_ENABLE_LOG_CONNECTIONS
              value: "no"
            - name: PGPOOL_ENABLE_LOG_HOSTNAME
              value: "yes"
            - name: PGPOOL_ENABLE_LOG_PER_NODE_STATEMENT
              value: "no"
            - name: PGPOOL_RESERVED_CONNECTIONS
              value: '1'
            - name: PGPOOL_CHILD_LIFE_TIME
              value: ""
            - name: PGPOOL_ENABLE_TLS
              value: "no"
            - name: PGPOOL_HEALTH_CHECK_PSQL_TIMEOUT
              value: "6"
          envFrom:
          ports:
            - name: postgresql
              containerPort: 5432
              protocol: TCP
          livenessProbe:
            failureThreshold: 5
            initialDelaySeconds: 30
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 5
            exec:
              command:
                - /opt/bitnami/scripts/pgpool/healthcheck.sh
          readinessProbe:
            failureThreshold: 5
            initialDelaySeconds: 5
            periodSeconds: 5
            successThreshold: 1
            timeoutSeconds: 5
            exec:
              command:
                - bash
                - -ec
                - 'PGPASSWORD=$(< $PGPOOL_POSTGRES_PASSWORD_FILE) psql -U "postgres" -d "postgres" -h /opt/bitnami/pgpool/tmp -tA -c "SELECT 1" >/dev/null'
          resources:
            limits:
              cpu: 375m
              ephemeral-storage: 2Gi
              memory: 384Mi
            requests:
              cpu: 250m
              ephemeral-storage: 50Mi
              memory: 256Mi
          volumeMounts:
            - name: empty-dir
              mountPath: /tmp
              subPath: tmp-dir
            - name: empty-dir
              mountPath: /opt/bitnami/pgpool/etc
              subPath: app-etc-dir
            - name: empty-dir
              mountPath: /opt/bitnami/pgpool/conf
              subPath: app-conf-dir
            - name: empty-dir
              mountPath: /opt/bitnami/pgpool/tmp
              subPath: app-tmp-dir
            - name: empty-dir
              mountPath: /opt/bitnami/pgpool/logs
              subPath: app-logs-dir
            - name: postgresql-password
              subPath: pgpool-password
              mountPath: /opt/bitnami/pgpool/secrets/pgpool-password
            - name: postgresql-password
              subPath: pgpool-sr-check-password
              mountPath: /opt/bitnami/pgpool/secrets/pgpool-sr-check-password
            - name: pgpool-password
              subPath: admin-password
              mountPath: /opt/bitnami/pgpool/secrets/admin-password
      volumes:
        - name: empty-dir
          emptyDir: {}
        - name: postgresql-password
          secret:
            secretName: pg-postgresql-ha-postgresql
            items:
              - key: password
                path: pgpool-password
              - key: repmgr-password
                path: pgpool-sr-check-password
        - name: pgpool-password
          secret:
            secretName: pg-postgresql-ha-pgpool
            items:
              - key: admin-password
                path: admin-password
---
# Source: postgresql-ha/templates/postgresql/statefulset.yaml
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: pg-postgresql-ha-postgresql
  namespace: "default"
  labels:
    app.kubernetes.io/instance: pg
    app.kubernetes.io/component: postgresql
    role: data
spec:
  replicas: 3
  podManagementPolicy: "Parallel"
  serviceName: pg-postgresql-ha-postgresql-headless
  updateStrategy:
    type: RollingUpdate
  selector:
    matchLabels:
      app.kubernetes.io/instance: pg
      app.kubernetes.io/component: postgresql
      role: data
  template:
    metadata:
      labels:
        app.kubernetes.io/instance: pg
        app.kubernetes.io/component: postgresql
        role: data
    spec:
      
      automountServiceAccountToken: false
      affinity:
        podAffinity:
          
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
            - podAffinityTerm:
                labelSelector:
                  matchLabels:
                    app.kubernetes.io/instance: pg
                    app.kubernetes.io/name: postgresql-ha
                    app.kubernetes.io/component: postgresql
                topologyKey: kubernetes.io/hostname
              weight: 1
        nodeAffinity:
          
      securityContext:
        fsGroup: 1001
        fsGroupChangePolicy: Always
        supplementalGroups: []
        sysctls: []
      serviceAccountName: pg-postgresql-ha
      hostNetwork: false
      hostIPC: false
      containers:
        - name: postgresql
          image: docker.io/bitnami/postgresql-repmgr:15.10.0
          imagePullPolicy: "IfNotPresent"
          securityContext:
            allowPrivilegeEscalation: false
            capabilities:
              drop:
              - ALL
            privileged: false
            readOnlyRootFilesystem: true
            runAsGroup: 1001
            runAsNonRoot: true
            runAsUser: 1001
            seLinuxOptions: {}
            seccompProfile:
              type: RuntimeDefault
          lifecycle:
            preStop:
              exec:
                command:
                  - /pre-stop.sh
                  - "25"
          # Auxiliary vars to populate environment variables
          env:
            - name: BITNAMI_DEBUG
              value: "false"
            # PostgreSQL configuration
            - name: POSTGRESQL_VOLUME_DIR
              value: "/bitnami/postgresql"
            - name: PGDATA
              value: "/bitnami/postgresql/data"
            - name: POSTGRES_USER
              value: "postgres"
            - name: POSTGRES_PASSWORD_FILE
              value: "/opt/bitnami/postgresql/secrets/password"
            - name: POSTGRES_DB
              value: "postgres"
            - name: POSTGRESQL_LOG_HOSTNAME
              value: "true"
            - name: POSTGRESQL_LOG_CONNECTIONS
              value: "false"
            - name: POSTGRESQL_LOG_DISCONNECTIONS
              value: "false"
            - name: POSTGRESQL_PGAUDIT_LOG_CATALOG
              value: "off"
            - name: POSTGRESQL_CLIENT_MIN_MESSAGES
              value: "error"
            - name: POSTGRESQL_SHARED_PRELOAD_LIBRARIES
              value: "pgaudit, repmgr"
            - name: POSTGRESQL_ENABLE_TLS
              value: "no"
            - name: POSTGRESQL_PORT_NUMBER
              value: "5432"
            # Repmgr configuration
            - name: REPMGR_PORT_NUMBER
              value: "5432"
            - name: REPMGR_PRIMARY_PORT
              value: "5432"
            - name: MY_POD_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: REPMGR_UPGRADE_EXTENSION
              value: "no"
            - name: REPMGR_PGHBA_TRUST_ALL
              value: "no"
            - name: REPMGR_MOUNTED_CONF_DIR
              value: "/bitnami/repmgr/conf"
            - name: REPMGR_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
            - name: REPMGR_PARTNER_NODES
              value: pg-postgresql-ha-postgresql-0.pg-postgresql-ha-postgresql-headless.$(REPMGR_NAMESPACE).svc.cluster.local,pg-postgresql-ha-postgresql-1.pg-postgresql-ha-postgresql-headless.$(REPMGR_NAMESPACE).svc.cluster.local,pg-postgresql-ha-postgresql-2.pg-postgresql-ha-postgresql-headless.$(REPMGR_NAMESPACE).svc.cluster.local,
            - name: REPMGR_PRIMARY_HOST
              value: "pg-postgresql-ha-postgresql-0.pg-postgresql-ha-postgresql-headless.$(REPMGR_NAMESPACE).svc.cluster.local"
            - name: REPMGR_NODE_NAME
              value: "$(MY_POD_NAME)"
            - name: REPMGR_NODE_NETWORK_NAME
              value: "$(MY_POD_NAME).pg-postgresql-ha-postgresql-headless.$(REPMGR_NAMESPACE).svc.cluster.local"
            - name: REPMGR_NODE_TYPE
              value: "data"
            - name: REPMGR_LOG_LEVEL
              value: "NOTICE"
            - name: REPMGR_CONNECT_TIMEOUT
              value: "5"
            - name: REPMGR_RECONNECT_ATTEMPTS
              value: "2"
            - name: REPMGR_RECONNECT_INTERVAL
              value: "3"
            - name: REPMGR_USERNAME
              value: "repmgr"
            - name: REPMGR_PASSWORD_FILE
              value: "/opt/bitnami/postgresql/secrets/repmgr-password"
            - name: REPMGR_DATABASE
              value: "repmgr"
            - name: REPMGR_FENCE_OLD_PRIMARY
              value: "no"
            - name: REPMGR_CHILD_NODES_CHECK_INTERVAL
              value: "5"
            - name: REPMGR_CHILD_NODES_CONNECTED_MIN_COUNT
              value: "1"
            - name: REPMGR_CHILD_NODES_DISCONNECT_TIMEOUT
              value: "30"
          envFrom:
          ports:
            - name: postgresql
              containerPort: 5432
              protocol: TCP
          livenessProbe:
            failureThreshold: 6
            initialDelaySeconds: 30
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 5
            exec:
              command:
                - bash
                - -ec
                - 'ps waux | grep "data standby clone" | grep -v grep || PGPASSWORD=$(< $POSTGRES_PASSWORD_FILE) psql -w -U "postgres" -d "postgres" -h 127.0.0.1 -p 5432 -c "SELECT 1"'
          readinessProbe:
            failureThreshold: 6
            initialDelaySeconds: 5
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 5
            exec:
              command:
                - bash
                - -ec
                - |
                  exec pg_isready -U "postgres" -h 127.0.0.1 -p 5432
                  [ -f /opt/bitnami/postgresql/tmp/.initialized ] || [ -f /bitnami/postgresql/.initialized ]
          resources:
            limits:
              cpu: 375m
              ephemeral-storage: 2Gi
              memory: 384Mi
            requests:
              cpu: 250m
              ephemeral-storage: 50Mi
              memory: 256Mi
          volumeMounts:
            - name: empty-dir
              mountPath: /tmp
              subPath: tmp-dir
            - name: empty-dir
              mountPath: /opt/bitnami/postgresql/conf
              subPath: app-conf-dir
            - name: empty-dir
              mountPath: /opt/bitnami/postgresql/tmp
              subPath: app-tmp-dir
            - name: empty-dir
              mountPath: /opt/bitnami/repmgr/conf
              subPath: repmgr-conf-dir
            - name: empty-dir
              mountPath: /opt/bitnami/repmgr/tmp
              subPath: repmgr-tmp-dir
            - name: empty-dir
              mountPath: /opt/bitnami/repmgr/logs
              subPath: repmgr-logs-dir
            - name: password
              mountPath: /opt/bitnami/postgresql/secrets/
            - name: data
              mountPath: /bitnami/postgresql
            - name: hooks-scripts
              mountPath: /pre-stop.sh
              subPath: pre-stop.sh
            - name: hooks-scripts
              mountPath: /readiness-probe.sh
              subPath: readiness-probe.sh
      volumes:
        - name: empty-dir
          emptyDir: {}
        - name: hooks-scripts
          configMap:
            name: pg-postgresql-ha-postgresql-hooks-scripts
            defaultMode: 0755
        - name: password
          secret:
            secretName: pg-postgresql-ha-postgresql
  volumeClaimTemplates:
    - apiVersion: v1
      kind: PersistentVolumeClaim
      metadata:
        name: data
      spec:
        accessModes:
          - "ReadWriteOnce"
        resources:
          requests:
            storage: "8Gi"
        storageClassName: sfsturbo-subpath-sc

在这里插入图片描述

kubectl get secret --namespace default pg-postgresql-ha-postgresql -o jsonpath="{.data.password}" | base64 -d && echo

在这里插入图片描述
进入容器执行如下命令查看pg复制情况：

psql -h 127.0.0.1 -U postgres --password -c "SELECT * FROM pg_stat_replication;"

在这里插入图片描述

PowerDesigner生成数据模型并导出报告
邓邓子的博客
08-25 3418
1、点击File->New Model… 2、创建模型 3、配置数据库连接 4、点击新增图标： 常见问题： 提示报错信息：您使用非管理权限登录。无法创建或修改System DSN 解决方法：已管理员方式运行PowerDesigner 5、选择系统数据源： 6、点击“下一页”，选中“MySQL ODBC 5.3 Unicode Driver”： 常见问题：无法找到MySQL驱动 解决方法：安装mysql-connector-odbc驱动 安装版本的位数要与PowerDesigner的位数一
4.Docker容器学习之Dockerfile入门到放弃
WeiyiGeek 唯一极客IT知识分享
10-09 1508
文章目录0x01 Dockerfile 编写1.基本结构与格式2.指令参数1)FROM - 基础镜像信息2)LABEL - 标签信息3)MAINTAINER - 维护者信息4)RUN - 镜像操作命令:5)CMD- 容器启动时执行指令6)EXPOSE - 端口映射指令7)env - 修改环境变量指令8)ARG - 构建参数9)ADD - 添加指定目录文件到容器指令10)COPY - 复制指定文件或者目录到容器中11)ENTRYPOINT - 配置容器启动进入后的执行命令-应用运行前的准备工作13)VOLUM
dify使用华为云OBS、Redis、PG
nangonghen的博客
03-05 379
使用华为云的服务作为dify的所有存储。
【K8S部署postgresql全过程】
最新发布
m0_73346222的博客
03-19 620
解析K8s部署PostgreSQL的关键技术栈，涵盖持久化存储、标签亲和性调度，敏感信息加密
Kubernetes集群安装高可用postgresql
热门推荐
weixin_46660849的博客
12-05 7万+
Kubernetes安装高可用postgresql集群
在k8s中实现posgresql集群及其负载均衡
adamho的专栏
08-02 1675
PostgreSQL是一种特性非常齐全的自由软件的对象-关系型数据库管理系统（
bitnami 的pgpool连接postgresql-ha出错SCRAM
mywebuser的专栏
04-15 2610
解决连接pgpool出现failed to authenticate with backend using SCRAM错误的解决过程
「在 Kubernetes 上运行 Pgpool-Il」实现 PostgreSQL 查询(读)负载均衡和连接池
o__cc的博客
02-28 656
介绍如何在 Kubernetes 上运行 Pgpool-II 实现 PostgreSQL 读查询负载均衡和连接池。 介绍 因为 PostgreSQL 是一个有状态的应用程序，并且管理 PostgreSQL 有非常具体的要求(例如备份、恢复、自动故障转移等)，Kubernetes 的内置功能无法处理这些任务。 因此，需要一个扩展 Kubernetes 功能以创建和管理 PostgreSQL 的 ...
一文学会主流Ansible Web UI的部署与使用 | 万字长文
NewTyun的博客
11-12 1万+
Ansible 作为近几年比较流行的自动化运维工具，由于简单、无侵入性，受到许多运维甚至开发同学的喜爱。大多数情况下，运维人员是喜欢直接在终端命令行下编写和执行playbook/role...
GaussDB性能调优实操：云原生数据库优化的终极指南
![GaussDB性能调优实操：云原生...本文旨在深入探讨GaussDB数据库的性能调优，涵盖了架构分析、性能指标监控、优化技术实践、故障诊断和高级调优策略。文章首先介绍了GaussDB的云原生架构，并对其关键性能指标进行
2020年MongoDB中文社区年终线上大会全纪录【附PPT及视频回放】
MongoDB中文社区
01-18 623
2021年1月8日，MongoDB中文社区联合MongoDB官方、锦木信息、Tapdata和华为开展2020年MongoDB中文社区年终大会。 点击下方链接 即可观看线上会议回放 http://www.itdks.com/Home/Act/apply?id=5533 大会要点回顾 会议开场由社区常委会委员、北京分会主席李丹给大家介绍社区的基本情况，MongoDB中文社区是由技术大会、技术培训、技术问答、原创博客、文档翻译和线上活动板块组成，是专注于MongoDB的...
基于K8S进行postgresql数据备份&恢复
qq_26375455的博客
04-07 2210
基于K8S进行postgresql数据备份&恢复1.前置说明2.进行备份和恢复的前置操作3.进行数据备份操作4.恢复备份数据5.如何进行数据的定时备份 1.前置说明 本文基于K8S进行postgres数据库进行备份和数据还原，数据库采用及集群HA的模式进行搭建，可参考前文Rancher+K8S+Docker集群搭建。其中涉及到psql、kubectl、crontab、pg_dumpall的基本操作。不熟悉的可以自行百度了解。 2.进行备份和恢复的前置操作 获取数据库所在命名空间$ kubectl
如何在Kubernetes中部署一个高可用的PostgreSQL集群环境
Kubernetes中文社区
03-22 6990
【编者的话】本文主要介绍了如何在Kubernetes环境中用Stolon去部署高可用的PostgreSQL，本文从Stolon的结构组成开始，由浅入深介绍原理，从开始安装到最后对其进行failover测试，深入浅出，为以后部署高可用的PostgreSQL提供了一种的解决方案。 创建一个高可用的PostgreSQL集群环境总是一件棘手的事情。在云环境里部署时更是非常困难。我至少找到了3
k8s集群下创建高可用postgresql数据库集群实践
davidqymo的博客
04-19 4851
K8s 安装 pg集群服务器 主要的目的是做到自动灾备切换，利用kubernetes 集群做到高可用的数据库服务。 三个节点， 2节点部署 proxy，sentinel，3节点keeper （DB） 本文选着stolon， 详细解决方案，原理请看：项目地址 https://github.com/sorintlab/stolon 总体架构架构 下面是步骤 1. 创建临时目录下载项目 mkdir ...
pgpool 之三 pgpool的几种模式
一名数据库爱好者的专栏
05-16 1338
pgpool:3.7.3 文档 http://www.pgpool.net/docs/latest/en/html/configuring-pgpool.html 4.3.2. Running mode of Pgpool-II There are four different running modes in Pgpool-II: streaming replication mode, ...
K8S部署高可用postgresql集群 —— 筑梦之路
筑梦之路
06-23 3110
git clone https://github.com/sorintlab/stolon.git 或者 git clone https://gitee.com/mirrors/stolon.git
k8s 部署PostgreSQL
weixin_42710740的博客
04-19 2764
k8s Unable to connect to the server: EOF 问题解决_灵耀的博客-CSDN博客 中介绍了如何在win10 中使用k8s 下面介绍k8s 使用 在环境env: - name: PGDATA value: /var/lib/postgresql/data/pgdata - name: POSTGRES_USER value: postgres...
pgpool-II主备流复制的架设
weixin_33985507的博客
06-16 254
1.环境 OS: CentOS release 6.4 (Final) DB： postgresql 9.3.6 pgpool服务器： pgpool 172.16.0.240 数据库主服务器：master 172.16.0.241 数据库从服务器：slave 172.16.0.242　 其中主从数据库使用的流复制，并且已经配置完毕，新配置的pgpool使用postgres用...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值