CHANGE DESCRIPTION

Upstream controller already enables huge_pages in PostgreSQL if instance has hugepage resource requests but PostgreSQL is not able to actually use hugepages. Because Kubernetes requires volumes and volume mounts for hugepages to make them usable in the container.

To test hugepages on GKE:

$ cat node-pool-config.yaml
linuxConfig:
  hugepageConfig:
    hugepage_size2m: 1024

$ gcloud container node-pools update default-pool --cluster <cluster> --location <region> --system-config-from-file=./node-pool-config.yaml

after the above operation completes create cluster with these resources:

    resources:
      limits:
        memory: 4Gi
        hugepages-2Mi: 2Gi

in my testing I needed to increase shared_buffers too:

  patroni:
    dynamicConfiguration:
      postgresql:
        parameters:
          shared_buffers: 1GB

you should see reserved hugepages in /proc/meminfo in database containers.

CHECKLIST

Jira

• Is the Jira ticket created and referenced properly?
• Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
• Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

• Is an E2E test/test case added for the new feature/change?
• Are unit tests added where appropriate?

Config/Logging/Testability

• Are all needed new/changed options added to default YAML files?
• Are all needed new/changed options added to the Helm Chart?
• Did we add proper logging messages for operator actions?
• Did we ensure compatibility with the previous version or cluster upgrade process?
• Does the change support oldest and newest supported PG version?
• Does the change support oldest and newest supported Kubernetes version?