-
Notifications
You must be signed in to change notification settings - Fork 1k
How to allocate hugepages resource in postgres-operator #1549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
After applying this patch on statefulset, Postgres container is creating successfully.
From this what I understand is, if we pass hugepages as a resource while creating a pod it’s working, and I don’t see an option in Postgres-operator to set it. please correct me if I am wrong. |
Even on kubernetes document, it is mentioned as we have to request a resource for hugepages. Is there any plan to support the feature to set hugepages resource limit from a manifest file? |
@alexeyklyukin @FxKu @RafiaSabih @mkabilov @Jan-M |
@sskurapati any status on this? |
I guess the simplest way to do this, is passing through the |
… to the statefulset (#2311) * Add hugepages-2Mi and 1Gi to ResourceDescription type and crd (#1549, #1788) * Add tests for hugepages resource requests/limits * Add tests for hugepages resource requests/limits on sidecars, too * Add docs for hugepages support * Add link to kubernetes docs on hugepages * Add tests for hugepages not being set on container if not requested in custom resource * Add hugepages resources fields to manifest docs * Add hugepages resources fields to complete manifest example * Add hugepages resources fields to chart crd --------- Co-authored-by: Felix Kunde <felix-kunde@gmx.de>
Please, answer some short questions which should help us to understand your problem / question better?
We are running all our services on centos 7 using docker-compose, now we are planning to use kubernetes.
I am running our pods on k8s on centos 7, and some of our pods require hugepages, so we enabled hugepages on the machine.
We are trying to use the Postgres operator for data-store deployment on Kubernetes. I am not able to allowcate hugepages resources in the operator.
While creating my own Postgres pod I can pass hugepages in resources like
How can I achieve it with Postgres-operator?
I am facing the following issue while creating Postgres cluster with operator:
The text was updated successfully, but these errors were encountered: