8000 Add helm chart k8s install info to readme by fatihbaltaci · Pull Request #201 · getanteon/anteon · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add helm chart k8s install info to readme #201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 15, 2023
Merged

Add helm chart k8s install info to readme #201

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion selfhosted/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,9 @@ This README provides instructions for installing and an overview of the system r

✅ **Dockerized**: Containerized solution simplifies deployment and reduces dependency management overhead.

✅ **Easy to Deploy**: Automated setup processes using Docker Compose.
✅ **Helm Chart**: [Helm chart](https://github.com/ddosify/ddosify-helm-charts) for Kubernetes deployments.

✅ **Easy to Deploy**: Automated setup processes using Docker Compose and Helm Charts.


## 🛠 Prerequisites
Expand Down Expand Up @@ -44,6 +46,10 @@ Ddosify Self Hosted starts in the background. You can access the dashboard at [h
curl -sSL https://raw.githubusercontent.com/ddosify/ddosify/master/selfhosted/install.sh | bash
```

## 🚀 Deploy on Kubernetes

You can deploy Ddosify Self Hosted on Kubernetes using the [Helm chart](https://github.com/ddosify/ddosify-helm-charts).

## 📖 Manual Installation

### 1. Clone the repository
Expand Down Expand Up @@ -125,6 +131,10 @@ docker run --name $NAME -dit \

You should see `mq_waiting_new_job` log in the engine container logs. This means that the engine is waiting for a job from the service server. After the engine is added, you can see it in the Engines page in the dashboard.

### **Example 3**: Adding the engine to Kubernetes

You can deploy the engine on Kubernetes using the Helm chart. Please check the [Ddosify Helm chart](https://github.com/ddosify/ddosify-helm-charts#add-new-engine-optional) repository for more information.

## 🧹 Remove New Engine

If you added new engines, you can remove them by running the following command. Change the docker container name `ddosify_hammer_1` to the name of the engine you added.
Expand Down
0