From d6ce66160b517d0f854bb910772eede00b772ec9 Mon Sep 17 00:00:00 2001 From: Naga Ravi Chaitanya Elluri Date: Wed, 10 Jul 2024 12:24:26 -0400 Subject: [PATCH] Remove podman-compose dependency We are not using it in the krkn code base and removing it fixes one of the license issues reported by FOSSA. This commit also removes setting up dependencies using docker/podman compose as it not actively maintained. Signed-off-by: Naga Ravi Chaitanya Elluri --- README.md | 12 ------------ docker-compose.yml | 31 ------------------------------- requirements.txt | 1 - 3 files changed, 44 deletions(-) delete mode 100644 docker-compose.yml diff --git a/README.md b/README.md index cc9f3ced..930d6256 100644 --- a/README.md +++ b/README.md @@ -41,18 +41,6 @@ After installation, refer back to the below sections for supported scenarios and #### Running Kraken with minimal configuration tweaks For cases where you want to run Kraken with minimal configuration changes, refer to [krkn-hub](https://github.com/krkn-chaos/krkn-hub). One use case is CI integration where you do not want to carry around different configuration files for the scenarios. -### Setting up infrastructure dependencies -Kraken indexes the metrics specified in the profile into Elasticsearch in addition to leveraging Cerberus for understanding the health of the Kubernetes cluster under test. More information on the features is documented below. The infrastructure pieces can be easily installed and uninstalled by running: - -``` -$ cd kraken -$ podman-compose up or $ docker-compose up # Spins up the containers specified in the docker-compose.yml file present in the run directory. -$ podman-compose down or $ docker-compose down # Delete the containers installed. -``` -This will manage the Cerberus and Elasticsearch containers on the host on which you are running Kraken. - -**NOTE**: Make sure you have enough resources (memory and disk) on the machine on top of which the containers are running as Elasticsearch is resource intensive. Cerberus monitors the system components by default, the [config](config/cerberus.yaml) can be tweaked to add applications namespaces, routes and other components to monitor as well. The command will keep running until killed since detached mode is not supported as of now. - ### Config Instructions on how to setup the config and the options supported can be found at [Config](docs/config.md). diff --git a/docker-compose.yml b/docker-compose.yml deleted file mode 100644 index c4d66e73..00000000 --- a/docker-compose.yml +++ /dev/null @@ -1,31 +0,0 @@ -version: "3" -services: - elastic: - image: docker.elastic.co/elasticsearch/elasticsearch:7.13.2 - deploy: - replicas: 1 - restart_policy: - condition: on-failure - network_mode: host - environment: - discovery.type: single-node - kibana: - image: docker.elastic.co/kibana/kibana:7.13.2 - deploy: - replicas: 1 - restart_policy: - condition: on-failure - network_mode: host - environment: - ELASTICSEARCH_HOSTS: "http://0.0.0.0:9200" - cerberus: - image: quay.io/openshift-scale/cerberus:latest - privileged: true - deploy: - replicas: 1 - restart_policy: - condition: on-failure - network_mode: host - volumes: - - ./config/cerberus.yaml:/root/cerberus/config/config.yaml:Z # Modify the config in case of the need to monitor additional components - - ${HOME}/.kube/config:/root/.kube/config:Z diff --git a/requirements.txt b/requirements.txt index f79beebe..5b19b395 100644 --- a/requirements.txt +++ b/requirements.txt @@ -22,7 +22,6 @@ oauth2client==4.1.3 pandas==2.2.0 openshift-client==1.0.21 paramiko==3.4.0 -podman-compose==1.0.6 pyVmomi==8.0.2.0.1 pyfiglet==1.0.2 pytest==8.0.0