* Added dataclasses to store info retrieved from k8 client calls
* Replaced few invoke commands in common_litmus
* Minor Documentation Changes
* Removed unused import and redundant variable
Signed-off-by: Shreyas Anantha Ramaprasad <ars.shreyas@gmail.com>
This commit updates Krkn source Dockerfile to copy azure client binary
from the official azure-cli image instead of using package manager to
avoid dependency issues.
Debug error occured when giving a bad network interface list
Traceback (most recent call last):
File "/root/kraken/run_kraken.py", line 318, in <module>
main(options.cfg)
File "/root/kraken/run_kraken.py", line 239, in main
network_chaos.run(scenarios_list, config, wait_duration)
File "/root/kraken/kraken/network_chaos/actions.py", line 39, in run
test_interface = verify_interface(test_interface, nodelst, pod_template)
File "/root/kraken/kraken/network_chaos/actions.py", line 111, in verify_interface
"Interface %s not found in node %s interface list %s" % (interface, nodelst[pod_index]),
TypeError: not enough arguments for format string
Signed-off-by: STARTX <clarue@startx.fr>
This commit:
- Leverages distribution flag in the config set by the user to skip
things not supported on OpenShift to be able to run scenarios on
Kubernetes.
- Adds sample config and scenario files that work on Kubernetes.
Since jinja2 3.1.0, escape need to be imported from MarkupSafe, which conflicts with flask1.x.x, so pining jinja2 to 3.0.3 to work with flask 1.x.x and latest version of werkzeug deprecates BaseResponse hence pining to 2.0.3.
Since import of JSON is deprecated from itsdangerous version 2.1.0 [1], this patch fixes the version to 2.0.1.
By fixing to version, we can avoid the below import error.
Error "from itsdangerous import json as _json ImportError: cannot import name 'json' from 'itsdangerous'"
[1] https://itsdangerous.palletsprojects.com/en/2.1.x/changes/#version-2-1-0
By default a jinja2 version less then 3.0.1 is installed, which raises error "cannot import name 'soft_unicode' from 'markupsafe'".
Using jinja2 3.0.1 or greater avoids this issue.
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.
