kube-monkey
litmus
kube-monkey | litmus | |
---|---|---|
9 | 63 | |
2,920 | 4,187 | |
- | 0.8% | |
3.4 | 9.4 | |
13 days ago | 6 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kube-monkey
-
Does your company have a Change Advisory Board (CAB)?
Not in the typical sense, but we have plenty of standard practices and cross-team checkpoints to limit risk. By the time we're deploying changes to production, the work has had a card created, assigned points (which necessarily involves discussing scope and risk), architected (as a group), code peer reviewed, hit unit tests (automated), integration tests (automated), functional tests (automated), smoke tested (automated) end-to-end tests (a few automated, but mostly manual by QA), acceptance tested (by QA and business), resilience tests (chaos engineering with kube-monkey), been deployed to at least 3 environments (with the same exact same artifacts, just with config changes), and monitored for failures (pod restarts, log anomalies, etc -- all automated). Deploy to production is well communicated, and ANY team can request a halt to the deploy if they have concerns.
- Kube-monkey: an implementation of Netflix's Chaos Monkey for Kubernetes clusters
-
What happens when a service fails in your infra, or in other words, do you practice chaos engineering?
Part of being a cloud native company means designing services for failure. What happens, for example, if the payment service/pod goes down? Do the rest of your services continue operating normally? One thing tools like kube-monkey does is automatically kill pods for you on a certain date at a certain time in order to plan for failure events. Just wondering if anyone has dove into the deep end with this type of tooling and really just gone all out, besides Netflix?
-
Chaos Mesh for chaos engineering in Kubernetes
Chaos Mesh is a popular solution (about 5k GitHub stars), but — obviously — not the only one. E.g., Litmus is a powerful platform to test many things, and kube-monkey might be a good option for more basic stuff.
-
How many of you actually test your infrastructure code? For those that do, what benefits did you discover that testing brings to your code base?
Exactly the kind of thing I love to see! Sounds like a great use case for a tool like kube-monkey as well.
- GitHub - asobti/kube-monkey: An implementation of Netflix's Chaos Monkey for Kubernetes clusters
- kube-monkey: An implementation of Netflix's Chaos Monkey for Kubernetes clusters
- 27 open-source tools that can make your Kubernetes workflow easier 🚀🥳
-
Awesome Kubernetes Resources
Kube Monkey
litmus
-
Building Resilience with Chaos Engineering and Litmus
Litmus, Gremlin, Chaos Mesh, and Chaos Monkey are all popular open-source tools used for chaos engineering. As we will be using AWS cloud infrastructure, we will also explore AWS Fault Injection Simulator (FIS). While they share the same goals of testing and improving the resilience of a system, there are some differences between them. Here are some comparisons:
-
Strategies for Writing More Effective Tests in Golang
This LFX quarter I got to get my hands on LitmusChaos, a CNCF incubating opensource project that dives deep on making cloud-native chaos-engineering accessible to multiple developer personas.
-
Introduction to Chaos Engineering
In 2010 Netflix developed a tool called "Chaos Monkey", whose goal was to randomly take down compute services (such as virtual machines or containers), part of the Netflix production environment, and test the impact on the overall Netflix service experience. In 2011 Netflix released a toolset called "The Simian Army", which added more capabilities to the Chaos Monkey, from reliability, security, and resiliency (i.e., Chaos Kong which simulates an entire AWS region going down). In 2012, Chaos Monkey became an open-source project (under Apache 2.0 license). In 2016, a company called Gremlin released the first "Failure-as-a-Service" platform. In 2017, the LitmusChaos project was announced, which provides chaos jobs in Kubernetes. In 2019, Alibaba Cloud announced ChaosBlade, an open-source Chaos Engineering tool. In 2020, Chaos Mesh 1.0 was announced as generally available, an open-source cloud-native chaos engineering platform. In 2021, AWS announced the general availability of AWS Fault Injection Simulator, a fully managed service to run controlled experiments.
-
Building a More Robust Apache APISIX Ingress Controller With Litmus Chaos
Litmus Chaos is an open-source Chaos Engineering framework that provides an infrastructure experimental framework to validate the stability of controllers and microservices architectures. It can simulate various environments, such as container-level and application-level environments, natural disasters, faults, and upgrades, to understand how the system responds to these changes. The framework can also explore the behavior changes between controllers and applications, and how controllers respond to challenges in specific states. Litmus Chaos offers convenient observability integration capabilities and is highly extensible.
-
Getting the Github Octernship
I am Pratik Singh, a final-year engineering student from Bangalore. I have been alumni of the pilot program of the Github Octernship. Back in 2021, it was called Github Externship. I worked for an organisation LitmusChaos
-
rootly Vs firehydrant, any experience?
https://litmuschaos.io/ (open source)
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 2/2
LitmusChaos, is a platform that helps you to run Chaos Engineering in your cluster to identify weaknesses and improvement opportunities.
-
From KubeCon to my first keynote as a DevRel
When the workshop was over, I headed back to the conference pavilion to attend the LitmusChaos Project Office Hours. These discussion events are great because they allow you to learn more about the project ask questions, meet the maintainers, and learn about new features and upcoming updates.
-
Reliability/chaos engineering tools
I don't have experience with the solutions you mentioned but I'll add one more to your list. It's Litmus which is open source... https://github.com/litmuschaos/litmus
-
Implement DevSecOps to Secure your CI/CD pipeline
Implement Chaos Mesh and Litmus chaos engineering framework to understand the behavior and stability of application in real-world use cases.
What are some alternatives?
chaoskube - chaoskube periodically kills random pods in your Kubernetes cluster.
chaos-mesh - A Chaos Engineering Platform for Kubernetes.
istio - Connect, secure, control, and observe services.
chaosmonkey - Chaos Monkey is a resiliency tool that helps applications tolerate random instance failures.
kube-bench - Checks whether Kubernetes is deployed according to security best practices as defined in the CIS Kubernetes Benchmark
aws-fis-templates-cdk - Collection of AWS Fault Injection Simulator (FIS) experiment templates deploy-able via the AWS CDK
skaffold - Easy and Repeatable Kubernetes Development
podtato-head - Demo App for TAG App Delivery
kube-burner - Kubernetes performance and scale test orchestration framework written in golang
backstage - Backstage is an open platform for building developer portals [Moved to: https://github.com/backstage/backstage]
quay - Build, Store, and Distribute your Applications and Containers
mentoring - 👩🏿🎓👨🏽🎓👩🏻🎓CNCF Mentoring: LFX Mentorship + Summer of Code