Following are a list of enhancements that we are planning to work on adding support in Krkn. Of course any help/contributions are greatly appreciated.
- Ability to run multiple chaos scenarios in parallel under load to mimic real world outages
- Centralized storage for chaos experiments artifacts
- Support for causing DNS outages
- Chaos recommender to suggest scenarios having probability of impacting the service under test using profiling results
- Chaos AI integration to improve test coverage while reducing fault space to save costs and execution time krkn-chaos-ai
- Support for pod level network traffic shaping
- Ability to visualize the metrics that are being captured by Kraken and stored in Elasticsearch
- Support for running all the scenarios of Kraken on Kubernetes distribution - see krkn-chaos#185, krkn-chaos#186
- Continue to improve Chaos Testing Guide in terms of adding best practices, test environment recommendations and scenarios to make sure the OpenShift platform, as well the applications running on top it, are resilient and performant under chaotic conditions.
- Switch documentation references to Kubernetes
- OCP and Kubernetes functionalities segregation
- Krknctl - client for running Krkn scenarios with ease
- AI Chat bot to help get started with Krkn and commands
- Ability to roll back cluster to original state if chaos fails
- Add recovery time metrics to each scenario for better regression analysis
- Add resiliency scoring to chaos scenarios ran on cluster
- Add AI-based Chaos Configuration Generator
- Introduce Security Chaos Engineering Scenarios
- Add AWS-native Chaos Scenarios (S3, Lambda, Networking)
- Unify Krkn Ecosystem under krknctl for Enhanced UX
- Build Web UI for Creating, Monitoring, and Reviewing Chaos Scenarios
- Add Predefined Chaos Scenario Templates (KRKN Chaos Library)