github/krkn
1
0
Fork 0
mirror of https://github.com/krkn-chaos/krkn.git synced 2026-08-25 09:27:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add roadmap for Kraken

Browse Source 
This commit adds a roadmap which walks through the features and enhancements that
are going to be added to Kraken in the immediate future in order to help users
understand where we need help as well as where the project is going.
This commit is contained in:
Naga Ravi Chaitanya Elluri
2022-01-31 09:39:07 -05:00
parent 3554ef505e
commit 8c7b19d37d
3 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+9
View File
@@ -108,6 +108,15 @@ In addition to checking the recovery and health of the cluster and components un
- 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
### Roadmap
Following is a list of enhancements that we are planning to work on adding support in Kraken. Of course any help/contributions are greatly appreciated.
- [Ability to visualize the metrics that are being captured by Kraken and stored in Elasticsearch](https://github.com/cloud-bulldozer/kraken/issues/124)
- Ability to shape the ingress network similar to how Kraken supports [egress traffic shaping](https://github.com/cloud-bulldozer/kraken/blob/master/docs/network_chaos.md) today
- Continue to improve [Chaos Testing Guide](https://cloud-bulldozer.github.io/kraken/) in terms of adding more best practices, test environment recommendations and scenarios to make sure OpenShift platform, as well the applications running on top it, are resilient and performant under chaotic conditions
- Support for running Kraken on Kubernetes distribution - see https://github.com/cloud-bulldozer/kraken/issues/185, https://github.com/cloud-bulldozer/kraken/issues/186
- Sweet logo for Kraken - see https://github.com/cloud-bulldozer/kraken/issues/195
### Contributions
We are always looking for more enhancements, fixes to make it better, any contributions are most welcome. Feel free to report or work on the issues filed on github.
docs/_config.yml
+1 -1
View File
@@ -1 +1 @@
theme: jekyll-theme-cayman
theme: jekyll-theme-cayman
docs/index.md
+1 -1
View File
@@ -23,7 +23,7 @@ Topology never changes.
The network is homogeneous.
Consistent resource usage with no spikes
The assumptions led to a number of outages in production environments in the past. The services suffered from poor performance or were inaccessible to the customers, leadingto missing Service Level Agreement uptime promises, revenue loss, and a degradation in the perceived reliability of said services..
The assumptions led to a number of outages in production environments in the past. The services suffered from poor performance or were inaccessible to the customers, leading to missing Service Level Agreement uptime promises, revenue loss, and a degradation in the perceived reliability of said services..
How can we best avoid this from happening? This is exactly where Chaos testing can add value