mirror of
https://github.com/krkn-chaos/krkn.git
synced 2026-02-14 18:10:00 +00:00
c3db7f236f
This releases includes the changes needed for the customer as well as number of other fixes and enhancements: - Support for VMware node sceanrios - Support for ingress traffic shaping - Other changes can be found at https://github.com/redhat-chaos/krkn/releases/tag/v1.1.0
Kraken image
Container image gets automatically built by quay.io at Kraken image.
Run containerized version
Refer instructions for information on how to run the containerized version of kraken.
Run Custom Kraken Image
Refer to instructions for information on how to run a custom containerized version of kraken using podman.
Kraken as a KubeApp
To run containerized Kraken as a Kubernetes/OpenShift Deployment, follow these steps:
- Configure the config.yaml file according to your requirements.
- Create a namespace under which you want to run the kraken pod using
kubectl create ns <namespace>. - Switch to
<namespace>namespace:- In Kubernetes, use
kubectl config set-context --current --namespace=<namespace> - In OpenShift, use
oc project <namespace>
- In Kubernetes, use
- Create a ConfigMap named kube-config using
kubectl create configmap kube-config --from-file=<path_to_kubeconfig> - Create a ConfigMap named kraken-config using
kubectl create configmap kraken-config --from-file=<path_to_kraken_config> - Create a ConfigMap named scenarios-config using
kubectl create configmap scenarios-config --from-file=<path_to_scenarios_folder> - Create a service account to run the kraken pod
kubectl create serviceaccount useroot. - In Openshift, add privileges to service account and execute
oc adm policy add-scc-to-user privileged -z useroot. - Create a Job using
kubectl apply -f kraken.ymland monitor the status usingoc get jobsandoc get pods.
NOTE: It is not recommended to run Kraken internal to the cluster as the pod which is running Kraken might get disrupted.