Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
memory leak on cluster-operator
See original GitHub issuehello,
cluster-operator pod seem have a memory leak according my dynatrace probe.
pod/strimzi-cluster-operator-597c48675d-49xjz 1/1 Running 18 18d
Do you think if I increase JVM size I can fix this behaviors ?
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
1371985 – Possible memory leak in openshift master process ...
Steps to Reproduce: 1. Create openshift cluster in AWS 2. Start tests which creates/builds/redeploys/delete projects and apps 3. Let it run for ...
Read more >IJ10601: CLSTRMGR MEMORY LEAKS - IBM
This apar fixes some clstrmgr memory leaks. The larger the cluster configuration (number of RGs and resources) the more likely the cluster will...
Read more >Kubernetes memory leak troubleshooting - Stack Overflow
I upgraded our cluster to 1.20.14 and noticed the memory leaks. We have 5 cronjobs running every minute and I placed them on...
Read more >2.7 Preventing Memory Leaks in C++ Code
Memory leaks occur when new memory is allocated dynamically and never deallocated. In C programs, new memory is allocated by the malloc or...
Read more >Heartbeat 8.1.0 Kubernetes Autodiscovery Memory Leak - Beats
Hello Heartbeat 8.1.0 has a memory leak with enabled Kubernetes autodiscovery and Openshift kills the container on memory limit reached.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes. 0.20.0 should still work for you. But 0.21.0 might not anymore. I’m afraid that we need to make the cut in order to be able to support new versions of Kubernetes. In particular, for example Kubernetes 1.22 will not support CRD v1beta1 and we need to start preparing for it.
It’s clear thank for your replies.