Comments (5)
/triage accepted
/assign @rexagod
from kube-state-metrics.
@zhoujoetan try excluding configmaps
and secrets
from the list of exported resources (--resources=
command line option).
At least for me it dropped initial memory usage from ~400Mib to 24Mib.
Both CLI and helm chart have them included by default.
In my case Helm charts (which store the manifests in secrets by defaults) history were the main culprit for the I could not confirm is pagination is used which may mitigate this issue.
Hope this helps.
from kube-state-metrics.
kube-state-metrics version: v2.3.0
@zhoujoetan It seems you're on an outdated version that's no longer supported. Could you switch to one of the supported versions (preferably the latest release) and verify this issue still persists for you?
from kube-state-metrics.
I have figured out the issue. We had a ton of configmaps objects that KSM read during startup time. Trimming those objects brought the memory usage back down. I am closing the issue now.
from kube-state-metrics.
@zhoujoetan When you sam Configmap objects, you mean this cluste-rwide or was it something specific? Also when you say trimming was it like deleting unwanted CMs, or removing data from these CMs?
from kube-state-metrics.
Related Issues (20)
- Request to support ASLR in Kube-state-metrics HOT 2
- Using k8s labels in prometheus rules expr HOT 1
- v2.11.0 docker image doesn't exist on registry.k8s.io/kube-state-metrics/kube-state-metrics HOT 2
- Kube Node Status NotReady detection HOT 2
- Chart missing for v2.11.0 HOT 3
- Allow Custom Resource State mode to filter on resource labels HOT 1
- CVE in v2.11.0 Image HOT 8
- sharding with a deployment with '--resources=pods' and '--node=""' does not fetch pending pods HOT 10
- [regression] /metrics port down when not existing CRD are listed in config file HOT 5
- kube-state-metrics with autosharding stops updating shards when the labels of the statefulset are updated HOT 20
- Generated Prometheus metrics output not meet with the requirements HOT 4
- Parse Nested Arrays does not work HOT 1
- Some kube-state-metrics shards are serving up stale metrics HOT 5
- Node selection for fully qualified node-names fails (--node=ip-xx-xx-xx-xx.myzone.com) HOT 2
- Cut 2.12.1 HOT 4
- Purpose of `kube_pod_status_ready{condition="unknown"}` HOT 13
- `kube_job_failed` should have `reason` label HOT 5
- Image link in README is outdated HOT 2
- Custom resource state metrics wildcard not working HOT 1
- Flux custom metrics monitoring broken in 2.12 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kube-state-metrics.