Install only the ServiceMonitor and PodMonitor Prometheus CRDs - #122
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A heap profile showed CRD and OpenAPI data is 83% of kube-apiserver live memory. The ten monitoring.coreos.com CRDs are a quarter of all CRD schema bytes, and eight of them have never held an object, since VictoriaMetrics owns alerting, rules and probes. victoria-metrics-operator 0.74 checks at startup which Prometheus kinds exist and skips converters for missing ones.
After merge, the ArgoCD app does not prune, so the eight CRDs need deleting by hand, then a restart of victoria-metrics-operator.