Presently, when a memory attack is performed against the Kubernetes pod of a given application, assuming the default configuration the Gremlin process is likely to be terminated rather than the application process.
This may change or become configurable in a future release.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article