-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Reject PrometheusRule objects that generate > 512KiB configmap #6478
Labels
Comments
@jtslear IIUC correctly your problem, you've got a PrometheusRule which by itself is above the 1MB limit? |
simonpasquier
changed the title
@simonpasquier the title of the issue was generic decently generic, I'm happy to open a new issue as I realize my proposed question is not directly related.
The operator fails to reconcile when a single PrometheusRule object generates > 1MB configmap
Apr 18, 2024
simonpasquier
changed the title
The operator fails to reconcile when a single PrometheusRule object generates > 1MB configmap
Reject PrometheusRule objects that generate > 1MB configmap
Apr 18, 2024
/assign |
yp969803
added a commit
to yp969803/prometheus-operator
that referenced
this issue
May 18, 2024
5 tasks
simonpasquier
changed the title
Reject PrometheusRule objects that generate > 1MB configmap
Reject PrometheusRule objects that generate > 512KB configmap
May 21, 2024
simonpasquier
changed the title
Reject PrometheusRule objects that generate > 512KB configmap
Reject PrometheusRule objects that generate > 512KiB configmap
May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The error is obvious:
In this case, the ruleset that the CRD is trying to create simply exceeds the 1MB limit for ConfigMaps. So I know the problem, but I'm hoping we can move this error to prior to the CRD accepting the change and thus failing the deployment. Otherwise, I don't know things are wrong until my attempt at looking at data showcases that I'm missing rules.
Originally posted by @jtslear in #5085 (comment)
The text was updated successfully, but these errors were encountered: