Value Statement

Iop requirements. refer to https://docs.google.com/document/d/1ZCbuTTZbRdRKomG_l78rxHiuDOJCq_1RPP_8MUSIv_k/edit?tab=t.0 

As an integrator, I can configure a database to use "logical" wal_level in order to support logical replication slots. they may want to have more configuration https://www.postgresql.org/docs/current/runtime-config-wal.html)

Definition of Done for Engineering Story Owner (Checklist)

• Support to read the customized postgres configmap. the name can be postgres-custom-config. the format is

  apiVersion: v1
  kind: ConfigMap
  metadata:
    name:   multicluster-global-hub-custom-postgresql-config
    namespace: multicluster-global-hub
  data:
    postgresql.conf: |
      wal_level=logical
      max_wal_size=10GB

• Merge the customized postgres configmap into postgres-config-configmap.yaml
• Not apply to BYO case

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [x] Unit/function tests have been automated and incorporated into the
  build.
• [x] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.