Closed psuriset closed 9 months ago
@prithvi1307 @umamukkara @ksatchit as leads of https://github.com/cncf/chaosengineering-wg it would be great to get your thoughts here.
Let's try to include the krkn contributors in the work you're pursuing on chaos/resiliency testing generally. Thanks!
Hello,
could you present the project in an upcoming TAG App Delivery meeting.
Additional note: the TOC would like more clarity on which repos are in scope for this project. Thanks!
@AloisReitbauer Absolutely we will add the demo to the agenda for next month's TAG App Delivery meeting. Thanks.
@amye https://github.com/redhat-chaos/krkn is the primary repository in scope.
There are other repos in redhat-chaos which are add-ons which can be integrated in krkn if needed:
@psuriset none of the other repos?
I'm excited to hear from krkn and @psuriset in TAG App Delivery and I believe testing and verification is indeed a part of application delivery. For example, LitmusChaos is managed by our TAG and there was even some effort to start a Chaos Engg WG with us.
But some testing frameworks like ChaosBlade and ChaosMesh are managed by TAG Security. Let's be sure we're aligned on where test and verification frameworks fit in our landscape.
@psuriset let's get you on the TAG schedule, I think there's still some time at our next general meeting on Wednesday 9/20. Here's the agenda/notes doc, add yourself and I'll let the other leads know: https://docs.google.com/document/d/1OykvqvhSG4AxEdmDMXilrupsX2n1qCSJUWwTc3I7AOs/edit
Thanks!
@jberkus Other repos are not in scope except the ones listed in this comment. https://github.com/cncf/sandbox/issues/44#issuecomment-1716007652
The TOC was unclear about which repos were being contributed. Recommend that you re-organize your project repositories and more clearly indicate what's here, as well as editing your application so that it is clear.
@amye Apologies for the confusion. We re-organized our project repos in our github org. Everything under this org belongs to krkn ecosystem which we would like to move to cncf. We will give admin access to this org once application is approved. We can also rename it to be more community centric. https://github.com/redhat-chaos
Updated the application as well. (cc: @jberkus )
Thank you @psuriset and team for presenting krkn to TAG App Delivery. Our writeup along with links to the recording and slides from the presentation are at https://github.com/cncf/tag-app-delivery/issues/465#issuecomment-1776075439.
The TAG believes krkn is a good fit for CNCF sandbox.
/vote-sandbox
@amye has called for a vote on [Sandbox] krkn
(#44).
The members of the following teams have binding votes: | Team |
---|---|
@cncf/cncf-toc |
Non-binding votes are also appreciated as a sign of support!
You can cast your vote by reacting to this
comment. The following reactions are supported:
In favor | Against | Abstain |
---|---|---|
👍 | 👎 | 👀 |
Please note that voting for multiple options is not allowed and those votes won't be counted.
The vote will be open for 7days
. It will pass if at least 66%
of the users with binding votes vote In favor 👍
. Once it's closed, results will be published here as a new comment.
@psuriset Please reach out to TAG Security to ensure they are aware of this project. Several other Chaos testing tools are aligned under TAG Security.
@joshgav would TAG App Delivery coordinate with TAG Security to clarify where chaos projects are homed?
/check-vote
So far 9.09%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
1 | 0 | 0 | 10 |
User | Vote | Timestamp |
---|---|---|
TheFoxAtWork | In favor | 2023-12-12 18:35:46.0 +00:00:00 |
@rochaporto | Pending | |
@mattfarina | Pending | |
@justincormack | Pending | |
@RichiH | Pending | |
@mauilion | Pending | |
@dzolotusky | Pending | |
@cathyhongzhang | Pending | |
@nikhita | Pending | |
@kgamanji | Pending | |
@erinaboyd | Pending |
Votes can only be checked once a day.
@psuriset Please reach out to TAG Security to ensure they are aware of this project. Several other Chaos testing tools are aligned under TAG Security.
@joshgav would TAG App Delivery coordinate with TAG Security to clarify where chaos projects are homed?
@TheFoxAtWork Sure thing, we will work with @joshgav to share Krkn project details with the TAG Security. Thanks!
/check-vote
Votes can only be checked once a day.
/check-vote
So far 27.27%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
3 | 0 | 0 | 8 |
User | Vote | Timestamp |
---|---|---|
cathyhongzhang | In favor | 2023-12-13 19:02:55.0 +00:00:00 |
TheFoxAtWork | In favor | 2023-12-12 18:35:46.0 +00:00:00 |
justincormack | In favor | 2023-12-13 15:54:07.0 +00:00:00 |
@rochaporto | Pending | |
@mattfarina | Pending | |
@RichiH | Pending | |
@mauilion | Pending | |
@dzolotusky | Pending | |
@nikhita | Pending | |
@kgamanji | Pending | |
@erinaboyd | Pending |
/check-vote
Votes can only be checked once a day.
/check-vote
Votes can only be checked once a day.
/check-vote
Votes can only be checked once a day.
/check-vote
So far 36.36%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
4 | 0 | 0 | 7 |
User | Vote | Timestamp |
---|---|---|
justincormack | In favor | 2023-12-13 15:54:07.0 +00:00:00 |
cathyhongzhang | In favor | 2023-12-13 19:02:55.0 +00:00:00 |
dzolotusky | In favor | 2023-12-15 14:59:12.0 +00:00:00 |
TheFoxAtWork | In favor | 2023-12-12 18:35:46.0 +00:00:00 |
@rochaporto | Pending | |
@mattfarina | Pending | |
@RichiH | Pending | |
@mauilion | Pending | |
@nikhita | Pending | |
@kgamanji | Pending | |
@erinaboyd | Pending |
/check-vote
So far 36.36%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
4 | 0 | 0 | 7 |
User | Vote | Timestamp |
---|---|---|
cathyhongzhang | In favor | 2023-12-13 19:02:55.0 +00:00:00 |
TheFoxAtWork | In favor | 2023-12-12 18:35:46.0 +00:00:00 |
justincormack | In favor | 2023-12-13 15:54:07.0 +00:00:00 |
dzolotusky | In favor | 2023-12-15 14:59:12.0 +00:00:00 |
@rochaporto | Pending | |
@mattfarina | Pending | |
@RichiH | Pending | |
@mauilion | Pending | |
@nikhita | Pending | |
@kgamanji | Pending | |
@erinaboyd | Pending |
/check-vote
Votes can only be checked once a day.
/check-vote
So far 54.55%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
6 | 0 | 0 | 5 |
User | Vote | Timestamp |
---|---|---|
kgamanji | In favor | 2023-12-17 13:14:40.0 +00:00:00 |
rochaporto | In favor | 2023-12-17 22:13:54.0 +00:00:00 |
TheFoxAtWork | In favor | 2023-12-12 18:35:46.0 +00:00:00 |
cathyhongzhang | In favor | 2023-12-13 19:02:55.0 +00:00:00 |
dzolotusky | In favor | 2023-12-15 14:59:12.0 +00:00:00 |
justincormack | In favor | 2023-12-13 15:54:07.0 +00:00:00 |
@mattfarina | Pending | |
@RichiH | Pending | |
@mauilion | Pending | |
@nikhita | Pending | |
@erinaboyd | Pending |
/check-vote
Votes can only be checked once a day.
/check-vote
Votes can only be checked once a day.
/check-vote
So far 63.64%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
7 | 0 | 0 | 4 |
User | Vote | Timestamp |
---|---|---|
cathyhongzhang | In favor | 2023-12-13 19:02:55.0 +00:00:00 |
justincormack | In favor | 2023-12-13 15:54:07.0 +00:00:00 |
TheFoxAtWork | In favor | 2023-12-12 18:35:46.0 +00:00:00 |
rochaporto | In favor | 2023-12-17 22:13:54.0 +00:00:00 |
dzolotusky | In favor | 2023-12-15 14:59:12.0 +00:00:00 |
mattfarina | In favor | 2023-12-18 13:58:22.0 +00:00:00 |
kgamanji | In favor | 2023-12-17 13:14:40.0 +00:00:00 |
@RichiH | Pending | |
@mauilion | Pending | |
@nikhita | Pending | |
@erinaboyd | Pending |
Please note @mauilion's vote was made in https://github.com/cncf/sandbox/issues/44#issuecomment-1858165359 instead of https://github.com/cncf/sandbox/issues/44#issuecomment-1852449483 and so is not being counted.
With that vote 8/11 are in favor and this should be accepted to sandbox.
The vote passed! 🎉
72.73%
of the users with binding vote were in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
8 | 0 | 0 | 3 |
User | Vote | Timestamp |
---|---|---|
@cathyhongzhang | In favor | 2023-12-13 19:02:55.0 +00:00:00 |
@TheFoxAtWork | In favor | 2023-12-12 18:35:46.0 +00:00:00 |
@erinaboyd | In favor | 2023-12-19 14:04:52.0 +00:00:00 |
@dzolotusky | In favor | 2023-12-15 14:59:12.0 +00:00:00 |
@justincormack | In favor | 2023-12-13 15:54:07.0 +00:00:00 |
@mattfarina | In favor | 2023-12-18 13:58:22.0 +00:00:00 |
@kgamanji | In favor | 2023-12-17 13:14:40.0 +00:00:00 |
@rochaporto | In favor | 2023-12-17 22:13:54.0 +00:00:00 |
Thank you accepting our project into CNCF Sandbox program.
Hi @psuriset ! Welcome aboard! We're very excited to get you onboarded as a CNCF sandbox project! Here's the link to your onboarding checklist: https://github.com/cncf/toc/issues/1228
Here you can communicate any questions or concerns you might have. Please don't hesitate to reach out, I am always happy to help!
Application contact emails
nelluri@redhat.com , briordan@redhat.com, psuriset@redhat.com
Project Summary
Krkn is a chaos and resiliency testing tool for Kubernetes with a focus on evaluating performance under load and scale
Project Description
Krkn is a chaos and resiliency testing tool for Kubernetes with a focus on evaluating performance under load and scale. It injects deliberate failures into the clusters to check if it is resilient to turbulent conditions and cluster as well as the components under test undergo minimal performance degradation to meet the SLOs and SLAs. In addition to performance and resiliency evaluation, health of the entire cluster is also checked as disruption of one component might have an impact on other components. Methodology is captured as part of the Chaos Testing Guide: https://redhat-chaos.github.io/krkn/.
Org repo URL
https://github.com/redhat-chaos
Project repo URL
All repos under in this org (https://github.com/redhat-chaos):
Primary project is krkn (https://github.com/redhat-chaos/krkn) & rest of them belong to krkn ecosystem.
Additional repos
Website URL
https://github.com/redhat-chaos/krkn and https://redhat-chaos.github.io/krkn/
Roadmap
https://github.com/redhat-chaos/krkn/blob/main/ROADMAP.md
Roadmap context
The roadmap items are prioritized based on the requests and feedback from the community. Each of the items added to the roadmap are thoroughly evaluated, discussed before adding the support in the tool.
Contributing Guide
https://github.com/redhat-chaos/krkn/blob/main/docs/contribute.md
Code of Conduct (CoC)
https://github.com/redhat-chaos/krkn/blob/main/CODE_OF_CONDUCT.md
Adopters
STARTX: French consulting and training company delivering expertise to build private and public cloud using Open-Source solutions. Red Hat: Engineering teams use it to chaos test Kubernetes, OpenShift and services running on top of it in CI environments like Prow. IBM Research: Engineering teams use it to develop chaos pipelines in software products - AI Framework integration to expand the capabilities after opening enhancements in Krkn and reviewed by maintainer and contributor Krkn team.
Contributing or Sponsoring Org
Red Hat Inc.
Maintainers file
https://github.com/redhat-chaos/krkn/blob/main/MAINTAINERS.md
IP Policy
Trademark and accounts
Why CNCF?
Our team firmly believes that Krkn is a valuable addition to the CNCF's impressive range of projects and could greatly benefit from support, oversight and direction that CNCF provides. The Krkn community would benefit from CNCF donation by allowing additional contributions and maintainers from the broader CNCF community. Krkn also provides features and capabilities that are not covered by other CNCF projects so the greater CNCF community would find Krkn’s adoption valuable as well. In addition, Krkn being part of CNCF will help adopt good principles of governance and get guidance to build it into an incubation level project moving forward.
Benefit to the Landscape
We would like to share the tooling and methodology of evaluating performance under chaotic conditions with the community involved in improving the performance, resilience and reliability of Kubernetes and services running on top of Kubernetes. As part of this, also maintain a chaos testing guide to help users get started: https://redhat-chaos.github.io/krkn/.
This will help the ecosystem and community in cross-pollinating the areas of resilience/chaos and performance for Kubernetes.
Cloud Native 'Fit'
No response
Cloud Native 'Integration'
No response
Cloud Native Overlap
Krkn share similar interests interms of chaos engineering with Litmus and Chaos-mesh but differs in terms of methodology especially considering performance as the main factor in addition to resilience.
Krkn provides the following capabilities that are not covered by Litmus or Chaos-mesh:
Similar projects
https://github.com/litmuschaos/litmus https://github.com/chaos-mesh/chaos-mesh
Product or Service to Project separation
Krkn is an 100% open source project with a focus on community and not a product. Currently it’s under redhat-chaos github organization but will be a separate repository if accepted for CNCF sandboxing.
Project presentations
Blog post on introduction to Kraken: https://www.openshift.com/blog/introduction-to-kraken-a-chaos-tool-for-openshift/kubernetes Discussion and demo on how Kraken can be leveraged to ensure Kubernetes/OpenShift is reliable, performant and scalable: https://www.youtube.com/watch?v=s1PvupI5sD0&ab_channel=OpenShift Blog post emphasizing the importance of making Chaos part of Performance and Scale runs to mimic the production environments: https://www.openshift.com/blog/making-chaos-part-of-kubernetes/openshift-performance-and-scalability-tests Blog post on findings from Chaos test runs: https://cloud.redhat.com/blog/openshift/kubernetes-chaos-stories
Project champions
No response
Additional information
No response