able to add the sidecar and initcontainer memory resources through HelmChart
with the operator helm charts(5.0.13 or 6.0.1) the sidecar and validate-arguments containers are getting resource empty and values.yaml doesn't have the resources set for the init and sidecar. if we don't set the values validation webhook is not allowing to create the pod.
warning FailedCreate 20s (x17 over 5m49s) statefulset-controller create Pod myminio-tenant-pool-0-0 in StatefulSet myminio-tenant-pool-0-0 failed error: admission webhook "validating-webhook.openpolicyagent.org" denied the request: the pod "myminio-tenant-pool-0-0", in namespace "minio-tenant", did not specify cpu limits resources, the pod "myminio-tenant-pool-0-0", in namespace "minio-tenant", did not specify cpu requests, the pod "myminio-tenant-pool-0-0", in namespace: "minio-tenant", did not specify memory limits resources, the pod "myminio-tenant-pool-0-0", in namespace: "monio-tenant", did not specify memory request resources. https://github.com/minio/operator/blob/v5.0.13/helm/operator/values.yaml
if we set the resourcequota at namespace level, we are getting below error.
Warning FailedCreate 100s (x17 over 7m8s) statefulset-controller create Pod myminio-tenant-pool-0-0 in StatefulSet myminio-pool-0 failed error: pod "myminio-tenant-pool-0-0" is forbidden: failed quots: minio-quota: must specify limits.cpu for : sidecar,validate-arguments; limits,memory for : sidecar,validat-arguments; requests,cpu for sidecar,validate-arguments; requestss,memory for: sidecar,validat-arguments
This was also reported in https://github.com/minio/operator/issues/1287#issuecomment-2278951782.
I guess you're using a custom pod admission controller?
correct @ramondeklein
Then it’s probably best for now to deploy the Tenant resource manually (without using Helm).
This seems like a pretty trivial addition to https://github.com/minio/operator/blob/master/helm/tenant/templates/tenant.yaml. Are you guys open to a contribution?
Although it's pretty trival, we are sceptical and try to address 95% of the use-cases using the Helm chart. If we need to support all edge-cases, then each property of the Helm chart will be configurable in the end and is almost impossible to maintain.
We'll discuss internally.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.
I am also affected with this issue deploying Minio from operator/tenant helm chart 71.1 via fleet on Rancher using project quotas.
Operator not able to deploy Tenant with the next error message:
create Pod minio-pool-0-0 in StatefulSet minio-pool-0 failed error: pods "minio-pool-0-0" is forbidden: failed quota: default-abu58: must specify limits.memory for: sidecar,validate-arguments
Please make it available to set the Tenant sidecar resources from helm values as well.
I guess you're using a custom pod admission controller?
Unfortunately in our case it is a standard rancher projekt quota, which does not let minio Tenant start because of missing resource limit settings...