Move images from redhat-chaos to krkn-chaos quay org

This commit also updates docs with the new references. Signed-off-by: Naga Ravi Chaitanya Elluri <[email protected]>
krkn-chaos · Jan 23, 2024 · b016f54 · b016f54
1 parent 5e20683
commit b016f54
Show file tree

Hide file tree

Showing 33 changed files with 118 additions and 148 deletions.
diff --git a/application-outages/Dockerfile b/application-outages/Dockerfile
@@ -1,8 +1,6 @@
 # Dockerfile for kraken
 
-FROM quay.io/redhat-chaos/krkn:latest
-
-MAINTAINER Red Hat Chaos Engineering Team
+FROM quay.io/krkn-chaos/krkn:latest
 
 ENV KUBECONFIG /root/.kube/config
 

diff --git a/cerberus/Dockerfile b/cerberus/Dockerfile
@@ -2,7 +2,7 @@
 
 FROM quay.io/redhat-chaos/cerberus:latest
 
-MAINTAINER Red Hat Chaos Engineering Team
+LABEL maintainer="Red Hat Chaos Engineering Team"
 
 ENV KUBECONFIG /root/.kube/config
 

diff --git a/chaos-recommender/Dockerfile b/chaos-recommender/Dockerfile
@@ -1,8 +1,6 @@
 # Dockerfile for kraken
 
-FROM quay.io/redhat-chaos/krkn:latest
-
-MAINTAINER Red Hat Chaos Engineering Team
+FROM quay.io/krkn-chaos/krkn:latest
 
 ENV KUBECONFIG /root/.kube/config
 

diff --git a/container-scenarios/Dockerfile b/container-scenarios/Dockerfile
@@ -1,8 +1,6 @@
 # Dockerfile for kraken
 
-FROM quay.io/redhat-chaos/krkn:latest
-
-MAINTAINER Red Hat Chaos Engineering Team
+FROM quay.io/krkn-chaos/krkn:latest
 
 ENV KUBECONFIG /root/.kube/config
 

diff --git a/docker-compose.yaml b/docker-compose.yaml
@@ -14,74 +14,74 @@ services:
       build:
           context: ./
           dockerfile: ./pod-scenarios/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:pod-scenarios
+      image: quay.io/krkn-chaos/krkn-hub:pod-scenarios
     node-scenarios:
         build:
             context: ./
             dockerfile: ./node-scenarios/Dockerfile
-        image: quay.io/redhat-chaos/krkn-hub:node-scenarios
+        image: quay.io/krkn-chaos/krkn-hub:node-scenarios
     zone-outages:
       build:
         context: ./
         dockerfile: ./zone-outages/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:zone-outages
+      image: quay.io/krkn-chaos/krkn-hub:zone-outages
     time-scenarios:
       build:
         context: ./
         dockerfile: ./time-scenarios/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:time-scenarios
+      image: quay.io/krkn-chaos/krkn-hub:time-scenarios
     power-outages:
       build:
         context: ./
         dockerfile: ./power-outages/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:power-outages
+      image: quay.io/krkn-chaos/krkn-hub:power-outages
     container-scenarios:
       build:
         context: ./
         dockerfile: ./container-scenarios/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:container-scenarios
+      image: quay.io/krkn-chaos/krkn-hub:container-scenarios
     node-cpu-hog:
       build:
         context: ./
         dockerfile: ./node-cpu-hog/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:node-cpu-hog
+      image: quay.io/krkn-chaos/krkn-hub:node-cpu-hog
     node-memory-hog:
       build:
         context: ./
         dockerfile: ./node-memory-hog/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:node-memory-hog
+      image: quay.io/krkn-chaos/krkn-hub:node-memory-hog
     node-io-hog:
       build:
         context: ./
         dockerfile: ./node-io-hog/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:node-io-hog
+      image: quay.io/krkn-chaos/krkn-hub:node-io-hog
     service-disruption-scenarios:
       build:
         context: ./
         dockerfile: ./service-disruption-scenarios/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:service-disruption-scenarios
+      image: quay.io/krkn-chaos/krkn-hub:service-disruption-scenarios
     application-outages:
       build:
         context: ./
         dockerfile: ./application-outages/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:application-outages
+      image: quay.io/krkn-chaos/krkn-hub:application-outages
     pvc-scenarios:
       build:
         context: ./
         dockerfile: ./pvc-scenario/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:pvc-scenarios
+      image: quay.io/krkn-chaos/krkn-hub:pvc-scenarios
     network-chaos:
       build:
         context: ./
         dockerfile: ./network-chaos/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:network-chaos
+      image: quay.io/krkn-chaos/krkn-hub:network-chaos
     pod-network-chaos:
       build:
         context: ./
         dockerfile: ./pod-network-chaos/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:pod-network-chaos
+      image: quay.io/krkn-chaos/krkn-hub:pod-network-chaos
     chaos-recommender:
       build:
         context: ./
         dockerfile: ./chaos-recommender/Dockerfile
-      image: quay.io/redhat-chaos/krkn-hub:chaos-recommender
+      image: quay.io/krkn-chaos/krkn-hub:chaos-recommender
diff --git a/docs/application-outages.md b/docs/application-outages.md
@@ -1,20 +1,20 @@
 ### Application outages
-This scenario disrupts the traffic to the specified application to be able to understand the impact of the outage on the dependent service/user experience. Refer [docs](https://github.com/redhat-chaos/krkn/blob/master/docs/application_outages.md) for more details.
+This scenario disrupts the traffic to the specified application to be able to understand the impact of the outage on the dependent service/user experience. Refer [docs](https://github.com/krkn-chaos/krkn/blob/master/docs/application_outages.md) for more details.
 
 #### Run
 
-If enabling [Cerberus](https://github.com/redhat-chaos/krkn#kraken-scenario-passfail-criteria-and-report) to monitor the cluster and pass/fail the scenario post chaos, refer [docs](https://github.com/redhat-chaos/krkn-hub/tree/main/docs/cerberus.md). Make sure to start it before injecting the chaos and set `CERBERUS_ENABLED` environment variable for the chaos injection container to autoconnect.
+If enabling [Cerberus](https://github.com/krkn-chaos/krkn#kraken-scenario-passfail-criteria-and-report) to monitor the cluster and pass/fail the scenario post chaos, refer [docs](https://github.com/krkn-chaos/krkn-hub/tree/main/docs/cerberus.md). Make sure to start it before injecting the chaos and set `CERBERUS_ENABLED` environment variable for the chaos injection container to autoconnect.
 
 ```
-$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:application-outages
+$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:application-outages
 $ podman logs -f <container_name or container_id> # Streams Kraken logs
 $ podman inspect <container-name or container-id> --format "{{.State.ExitCode}}" # Outputs exit code which can considered as pass/fail for the scenario
 ```
 
 ```
-$ docker run $(./get_docker_params.sh) --name=<container_name> --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:application-outages
+$ docker run $(./get_docker_params.sh) --name=<container_name> --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:application-outages
 OR 
-$ docker run -e <VARIABLE>=<value> --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:application-outages
+$ docker run -e <VARIABLE>=<value> --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:application-outages
 
 $ docker logs -f <container_name or container_id> # Streams Kraken logs
 $ docker inspect <container-name or container-id> --format "{{.State.ExitCode}}" # Outputs exit code which can considered as pass/fail for the scenario
@@ -41,7 +41,7 @@ BLOCK_TRAFFIC_TYPE      | It can be Ingress or Egress or Ingress, Egress ( needs
 
 **NOTE** In case of using custom metrics profile or alerts profile when `CAPTURE_METRICS` or `ENABLE_ALERTS` is enabled, mount the metrics profile from the host on which the container is run using podman/docker under `/root/kraken/config/metrics-aggregated.yaml` and `/root/kraken/config/alerts`. For example:
 ```
-$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-custom-metrics-profile>:/root/kraken/config/metrics-aggregated.yaml -v <path-to-custom-alerts-profile>:/root/kraken/config/alerts -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:application-outages
+$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-custom-metrics-profile>:/root/kraken/config/metrics-aggregated.yaml -v <path-to-custom-alerts-profile>:/root/kraken/config/alerts -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:application-outages
 ```
 
 #### Demo

diff --git a/docs/cerberus.md b/docs/cerberus.md
@@ -1,18 +1,18 @@
 # Cerberus
 
-[Cerberus](https://github.com/redhat-chaos/cerberus) monitors the cluster health and provides a go/no-go signal in addition to exposing cluster state metrics API.
+[Cerberus](https://github.com/krkn-chaos/cerberus) monitors the cluster health and provides a go/no-go signal in addition to exposing cluster state metrics API.
 Run the container on the same host on which chaos injection container is running, it runs as a daemon continuosly monitoring the cluster.
 
-**NOTE** Make sure to start it before injecting the chaos and set `CERBERUS_ENABLED` environment variable to autoconnect to the chaos injection container and other supported environment variables to tweak the components being monitored. 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. More details can be found [here](https://github.com/redhat-chaos/cerberus#how-does-cerberus-report-cluster-health).
+**NOTE** Make sure to start it before injecting the chaos and set `CERBERUS_ENABLED` environment variable to autoconnect to the chaos injection container and other supported environment variables to tweak the components being monitored. 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. More details can be found [here](https://github.com/krkn-chaos/cerberus#how-does-cerberus-report-cluster-health).
 
 ```
-$ podman run --net=host --env-host=true --privileged -d -v <path-to-kube-config>:/root/.kube/config:Z quay.io/redhat-chaos/cerberus:kraken-hub
+$ podman run --net=host --env-host=true --privileged -d -v <path-to-kube-config>:/root/.kube/config:Z quay.io/krkn-chaos/cerberus:kraken-hub
 ```
 
 ```
-$ docker run $(./get_docker_params.sh) --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/openshift-scale/cerberus:kraken-hub
+$ docker run $(./get_docker_params.sh) --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/cerberus:kraken-hub
 OR
-$ docker run -e VARIABLE=value --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/openshift-scale/cerberus:kraken-hub
+$ docker run -e VARIABLE=value --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/cerberus:kraken-hub
 ```
 
 #### Supported Parameters

diff --git a/docs/chaos-recommender.md b/docs/chaos-recommender.md
@@ -3,7 +3,7 @@ This tool profiles an application and gathers telemetry data such as CPU, Memory
 #### Run
 
 ```
-$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-kube-config>:/root/.kube/config:Z  -e NAMESPACE=<NAMESPACE> -e PROMETHEUS_ENDPOINT=<PROMETHEUS_ENDPOINT> -e PROMETHEUS_TOKEN=<PROMETHEUS_TOKEN>  quay.io/redhat-chaos/krkn-hub:chaos-recommender
+$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-kube-config>:/root/.kube/config:Z  -e NAMESPACE=<NAMESPACE> -e PROMETHEUS_ENDPOINT=<PROMETHEUS_ENDPOINT> -e PROMETHEUS_TOKEN=<PROMETHEUS_TOKEN>  quay.io/krkn-chaos/krkn-hub:chaos-recommender
 ```
 
 #### Supported parameters

diff --git a/docs/container-scenarios.md b/docs/container-scenarios.md
@@ -2,18 +2,18 @@
 This scenario disrupts the containers matching the label in the specified namespace on a Kubernetes/OpenShift cluster.
 
 #### Run
-If enabling [Cerberus](https://github.com/redhat-chaos/krkn#kraken-scenario-passfail-criteria-and-report) to monitor the cluster and pass/fail the scenario post chaos, refer [docs](https://github.com/redhat-chaos/krkn-hub/tree/main/docs/cerberus.md). Make sure to start it before injecting the chaos and set `CERBERUS_ENABLED` environment variable for the chaos injection container to autoconnect.
+If enabling [Cerberus](https://github.com/krkn-chaos/krkn#kraken-scenario-passfail-criteria-and-report) to monitor the cluster and pass/fail the scenario post chaos, refer [docs](https://github.com/redhat-chaos/krkn-hub/tree/main/docs/cerberus.md). Make sure to start it before injecting the chaos and set `CERBERUS_ENABLED` environment variable for the chaos injection container to autoconnect.
 
 ```
-$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:container-scenarios
+$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:container-scenarios
 $ podman logs -f <container_name or container_id> # Streams Kraken logs
 $ podman inspect <container-name or container-id> --format "{{.State.ExitCode}}" # Outputs exit code which can considered as pass/fail for the scenario
 ```
 
 ```
-$ docker run $(./get_docker_params.sh) --name=<container_name> --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:container-scenarios
+$ docker run $(./get_docker_params.sh) --name=<container_name> --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:container-scenarios
 OR 
-$ docker run -e <VARIABLE>=<value> --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:container-scenarios
+$ docker run -e <VARIABLE>=<value> --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:container-scenarios
 
 $ docker logs -f <container_name or container_id> # Streams Kraken logs
 $ docker inspect <container-name or container-id> --format "{{.State.ExitCode}}" # Outputs exit code which can considered as pass/fail for the scenario
@@ -39,7 +39,7 @@ EXPECTED_RECOVERY_TIME  | Time to wait before checking if all containers that we
 
 **NOTE** In case of using custom metrics profile or alerts profile when `CAPTURE_METRICS` or `ENABLE_ALERTS` is enabled, mount the metrics profile from the host on which the container is run using podman/docker under `/root/kraken/config/metrics-aggregated.yaml` and `/root/kraken/config/alerts`. For example:
 ```
-$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-custom-metrics-profile>:/root/kraken/config/metrics-aggregated.yaml -v <path-to-custom-alerts-profile>:/root/kraken/config/alerts -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:container-scenarios
+$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-custom-metrics-profile>:/root/kraken/config/metrics-aggregated.yaml -v <path-to-custom-alerts-profile>:/root/kraken/config/alerts -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:container-scenarios
 ```
 
 

diff --git a/docs/network-chaos.md b/docs/network-chaos.md
@@ -1,17 +1,17 @@
 ### Network Chaos scenario
-This scenario introduces network latency, packet loss, bandwidth restriction in the egress traffic of a Node's interface using the tc and Netem. For more information refer the following [documentation](https://github.com/redhat-chaos/krkn/blob/master/docs/network_chaos.md).
+This scenario introduces network latency, packet loss, bandwidth restriction in the egress traffic of a Node's interface using the tc and Netem. For more information refer the following [documentation](https://github.com/krkn-chaos/krkn/blob/master/docs/network_chaos.md).
 
 #### Run
-If enabling [Cerberus](https://github.com/redhat-chaos/krkn#kraken-scenario-passfail-criteria-and-report) to monitor the cluster and pass/fail the scenario post chaos, refer [docs](https://github.com/redhat-chaos/krkn-hub/tree/main/docs/cerberus.md). Make sure to start it before injecting the chaos and set `CERBERUS_ENABLED` environment variable for the chaos injection container to autoconnect.
+If enabling [Cerberus](https://github.com/krkn-chaos/krkn#kraken-scenario-passfail-criteria-and-report) to monitor the cluster and pass/fail the scenario post chaos, refer [docs](https://github.com/redhat-chaos/krkn-hub/tree/main/docs/cerberus.md). Make sure to start it before injecting the chaos and set `CERBERUS_ENABLED` environment variable for the chaos injection container to autoconnect.
 
 ```
-$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:network-chaos
+$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:network-chaos
 $ podman logs -f <container_name or container_id> # Streams Kraken logs
 $ podman inspect <container-name or container-id> --format "{{.State.ExitCode}}" # Outputs exit code which can considered as pass/fail for the scenario
 ```
 
 ```
-$ docker run -e <VARIABLE>=<value> --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:network-chaos
+$ docker run -e <VARIABLE>=<value> --net=host -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:network-chaos
 
 $ docker logs -f <container_name or container_id> # Streams Kraken logs
 $ docker inspect <container-name or container-id> --format "{{.State.ExitCode}}" # Outputs exit code which can considered as pass/fail for the scenario
@@ -59,5 +59,5 @@ WAIT_DURATION           | Ensure that it is at least about twice of test_duratio
 
 **NOTE** In case of using custom metrics profile or alerts profile when `CAPTURE_METRICS` or `ENABLE_ALERTS` is enabled, mount the metrics profile from the host on which the container is run using podman/docker under `/root/kraken/config/metrics-aggregated.yaml` and `/root/kraken/config/alerts`. For example:
 ```
-$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-custom-metrics-profile>:/root/kraken/config/metrics-aggregated.yaml -v <path-to-custom-alerts-profile>:/root/kraken/config/alerts -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/redhat-chaos/krkn-hub:container-scenarios
+$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-custom-metrics-profile>:/root/kraken/config/metrics-aggregated.yaml -v <path-to-custom-alerts-profile>:/root/kraken/config/alerts -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:container-scenarios
 ```