-
Notifications
You must be signed in to change notification settings - Fork 506
set resource requests/limits for target-allocator #1103
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
I ran the target allocator on a larger cluster (200+ servicemonitors). |
@seankhliao would you like to fix it? |
tbh I'm not sure how I would fix it in the current structure of the CRD. ref: https://cloud-native.slack.com/archives/C033BJ8BASU/p1666986594165909 |
@seankhliao, can I work on it? |
sure |
@yuriolisa are you or anyone else working on it? |
Our k8s clusters run with
ResourceQuota
s, but the deployments created by for the target allocator don't have any set, so they're blocked from creation (at the ReplicaSet level which isn't reported back upwards)The text was updated successfully, but these errors were encountered: