Default requests/limits for containers in PostgresCluster CR

[jeremych1000]

Default requests/limits for containers in PostgresCluster CR

[Mahidhar-K]

I'm also looking for this information, but it seems to be missing from the crunchy documentation.
Could someone shed some light on the defaults that can be assigned to all containers, including main containers, sidecars, and init containers?
I'm curious about the reasons behind having multiple containers and which ones are mandatory, especially when it comes to sidecars.
I'd like to hear about the advantages and disadvantages of using sidecars versus not using them.

• pgo
• pgo upgrade
• database
• replication-cert-copy
• pgbackrest-config
• pgbackrest
• pg-backup-repo-host
• exporter
• Init container 1 - postgres-startup
• Init container 2 - nss-wrapper-init

Lastly, pgo upgrade pod is not seen in the pgo 5.5 manifest files? is this expected?

[jeremych1000]

Ok I've fixed it. Was missing the sidecar resources. Will leave this open for now so that @Mahidhar-K 's question can be answered as I'm interested in it as well.

in instances:
      sidecars:
        replicaCertCopy:
          resources:
            requests:
              cpu: 50m
              memory: 10Mi
            limits:
              memory: 30Mi

in backups:
      sidecars:
        pgbackrestConfig:
          resources:
            requests:
              cpu: 50m
              memory: 10Mi
            limits:
              memory: 50Mi
        pgbackrest:
          resources:
            {{- toYaml .Values.postgres.backups.resources | nindent 12 }}

[ValClarkson]

Hi @jeremych1000 and @Mahidhar-K, I'm going to close out this issue since it has been resolved and @Mahidhar-K that is a great question/conversation for our PGO project community discord server!