krkn-chaos / krkn-hub Goto Github PK

Misspelled variable name in the following link:
https://github.com/redhat-chaos/krkn-hub/blob/main/docs/node-memory-hog.md#supported-parameters

Says LIMTUS_INSTALL (vs LITMUS_INSTALL)

We need a mechanism in place to build container images based on the pull request commits to be able to test it for every PR instead of doing the same manually.

NOTE: https://github.com/arcalot/arcaflow-plugin-image-builder can be used as a reference for implementation.

Kraken-hub needs to support the metrics collection and evaluation features in Kraken to be able to capture metrics of interest from in-cluster prometheus and also evaluate them to determine pass/fail: https://github.com/cloud-bulldozer/kraken#scraping-and-storing-metrics-long-term and https://github.com/cloud-bulldozer/kraken#alerts.

Want to add a common run bash file at the base level with common functions that each run.sh script will use to avoid duplication

Can start with the following functions but could be more

# Check if oc is installed
log "Checking if OpenShift client is installed"
which oc &>/dev/null
if [[ $? != 0 ]]; then
  log "Looks like OpenShift client is not installed, please install before continuing"
  log "Exiting"
  exit 1
fi

# Check if kubectl is installed
log "Checking if kubernetes client is installed"
which kubectl &>/dev/null
if [[ $? != 0 ]]; then
  log "Looks like Kubernetes client is not installed, please install before continuing"
  log "Exiting"
  exit 1
fi

# Check if cluster exists and print the clusterversion under test
kubectl get clusterversion
if [[ $? -ne 0 ]]; then
  log "Unable to connect to the cluster, please check if it's up and make sure the KUBECONFIG is set correctly"
  exit 1
fi

Kraken-hub should support ingress based network chaos scenarios now that Kraken supports it - krkn-chaos/krkn#299.

Kraken now supports OCM/ACM chaos scenarios - krkn-chaos/krkn#370, we will need to get them into Kraken-hub as well to be able to run them using podman without having to carry around or tweak config files - especially useful for CI use case.

Kraken now support node scenarios for nodes/clusters in VMWare, it would be nice if we can add this support in krkn-hub to start leveraging node scenarios using krkn-hub wrapper.

We need to add a short demo of Kraken-hub in the github readme, this will help with giving a quick overview of capabilities of the tooling without having to go over the docs. https://asciinema.org/ might help with this.

When we trigger a cpu/mem hog scenario, one pod is scheduled in the default namespace. After the scenario is completed, this pods keeps lying there and isn't removed.

In my view, this pod should be removed/cleaned once the scenario test is completed.

To verify, after the scenario is completed run $ oc get pods -n default

In the document https://github.com/redhat-chaos/krkn-hub/blob/main/docs/cerberus.md#cerberus
The history port should be 8080, so:
"It exposes the go/no-go signal at http://0.0.0.0:8080/ and metrics API at http://0.0.0.0:8080/history."

By the way, the document is really helpful. Thank you for your sharing!

While testing the node memory hog scenario, container always gets created on random node. When verified it is due to the input.yaml template file has selector hard coded as none {}.

https://github.com/redhat-chaos/krkn-hub/blob/main/node-memory-hog/input.yaml.template

Similar file in cpu hog scenario has the variable assigned in the yaml and is working as expected. This has to be updated so to make sure the required node has the memory stress.

After PR: krkn-chaos/krkn#395 gets merged we will need to update the pointers of the cpu, memory and io hog to the new scenarios and add the new parameters for this

Will want to take out any refernces to litmus

https://github.com/redhat-chaos/krkn-hub/blob/main/pod-scenarios/pod_scenario.yaml.template needs to be replaced now that we use Arcaflow based pod-scenarios: krkn-chaos/krkn#280.

Add in Ci to validate kraken-hub scenarios and environment variables

In the node/mem/io hog scenarios, below two images are called internally from the parent image i.e.,

• quay.io/arcalot/arcaflow-plugin-kubeconfig:0.2.0
• quay.io/arcalot/arcaflow-plugin-stressng:0.3.1

In disconnected environments, these images will be pulled from a connected host and mirrored on to a local registry. The image names will have to be changed in order to pull it from the local mirror, instead of Quay.

Add ability to pass the wait time parameter to the container scenario in kraken hub