julienLemarie opened a new issue, #32859:
URL: https://github.com/apache/superset/issues/32859
### Bug description
Hello,
When I want to deploy superset, here is an extract of my values:
```superset:
init:
resources:
requests:
cpu: 0.1
memory: 256Mi
limits:
cpu: 0.5
memory: 512Mi
resources:
requests:
cpu: 0.1
memory: 256Mi
limits:
cpu: 0.5
memory: 512Mi
```
but resources are not affected to the "wait-for-postgres" pod (and there is
policies on my Kubernetes):
```
Error creating: pods "connect-superset-init-db-zlc4c" is forbidden: failed
quota: ***: must specify
limits.cpu for: wait-for-postgres;
limits.memory for: wait-for-postgres;
requests.cpu for: wait-for-postgres;
requests.memory for: wait-for-postgres
```
I was thinking because _wait-for-postgres_ `initContainers ` is in `init`,
there was inheritance but seems not.
Any ideas ?
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [ ] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
