{"id":383196,"date":"2020-11-17T10:47:18","date_gmt":"2020-11-17T15:47:18","guid":{"rendered":"http:\/\/www.marketnewsdesk.com\/?p=383196"},"modified":"2020-11-17T10:47:18","modified_gmt":"2020-11-17T15:47:18","slug":"gremlin-soundproofs-kubernetes-by-helping-devops-teams-isolate-noisy-neighbors-within-a-cluster","status":"publish","type":"post","link":"https:\/\/www.marketnewsdesk.com\/index.php\/gremlin-soundproofs-kubernetes-by-helping-devops-teams-isolate-noisy-neighbors-within-a-cluster\/","title":{"rendered":"Gremlin Soundproofs Kubernetes by Helping DevOps Teams Isolate Noisy Neighbors Within a Cluster"},"content":{"rendered":"

\n55% of Gremlin customers run Chaos Engineering experiments on Kubernetes to mitigate failure and optimize performance
\n<\/h2>\n
\n

San Jose, CA, Nov. 17, 2020 (GLOBE NEWSWIRE) — Gremlin<\/a>, a platform for safely and securely running Chaos Engineering experiments, today announced new features to \u201csoundproof\u201d Kubernetes and help engineers prevent noisy neighbors in a cluster. The idea of sharing resources across machines is not new or unique to Kubernetes; however, given the highly dynamic and ephemeral nature of containers orchestrated by Kubernetes, which can host dozens of apps and hundreds of services across a single cluster, sharing resources and security permissions is an even larger concern. <\/p>\n

According to recent Kubernetes Adoption Research<\/a>, 59% of large organizations use Kubernetes in production, which mirrors the distribution of companies running chaos attacks on the Gremlin platform. Gartner predicts in their CTO\u2019s Guide to Containers and Kubernetes that \u201cby 2025, more than 85% of global organizations will be running containerized applications in production, which is a significant increase from fewer than 35% in 2019.\u201d <\/p>\n

Besides being highly flexible and scalable, Kubernetes adoption is driven by resource efficiency: containers have a smaller resource footprint, which enables a much higher tenant density on a host, thereby increasing infrastructure utilization. But that density and utilization of resources adds to the \u201cnoisy neighbor\u201d problem, where one scaling or problematic service can impact another on the same node within a cluster. Without doing proactive testing, it’s difficult to know how a system handles a noisy neighbor in production, unless there is a spike in demand on a single service, at which point it\u2019s too late and customers already feel the impact. <\/p>\n

\u201cKubernetes is becoming the default way to build and operate applications at many enterprises, but along with the advantage of abstraction comes uncertainty,\u201d said Lorne Kligerman, Sr Director of Product at Gremlin. \u201cWe\u2019re providing DevOps teams with better tooling to understand how their Kubernetes applications will behave under various stresses, such as when a neighboring container is spiking with traffic.\u201d <\/p>\n

The noisy neighbor problem also introduces security concerns. Performing chaos experiments in multi-tenant environments requires fine-grained controls. Ideally, individuals and teams are limited to the namespaces where they should be performing attacks. Using namespace access control ensures that only team members with correct permissions will have access to specific Kubernetes objects, versus all objects in the cluster. This is crucial to ensuring the Chaos Engineering work an engineer is doing isn\u2019t negatively impacting neighboring services. <\/p>\n

Highlights<\/u>
<\/strong><\/p>\n