CrunchyData / postgres-operator

Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
https://access.crunchydata.com/documentation/postgres-operator/v5/
Apache License 2.0
3.97k stars 595 forks source link

How can we apply values for resources cpu and memory request and limits to the postgres operator #2131

Closed kseswar closed 3 years ago

kseswar commented 3 years ago

On how we can apply values of resource cpu and memory requests and limits to the postgres-operator ( currently we are manually editing the postgres-operator deployment using the command kubectl edit deployment )

Please tell us about your environment:

Operating System: Linux based Where is this running ( Local, Cloud Provider) - GCP GKE cluster Storage being used (NFS, Hostpath, Gluster, etc):GCP PVC, Container Image Tag: centos7-4.3.0 / centos7-12.2-4.3.0 PostgreSQL Version:12.2 Platform (Docker, Kubernetes, OpenShift): Kubernetes Platform Version: 1.16.11-gke.5

jkatz commented 3 years ago

This is covered extensively in the documentation, but to benefit from this you will need to update to a supported version of the latest in the 4.3.x series.

kseswar commented 3 years ago

Hi, Thank you for sharing the link. I have already reviewed this document. My question is specific to the operator pod itself. The documentation only talks about the cluster it does not specify the operator pod