consolidated more variables and deleted all hard-coded values
This commit is contained in:
10
README.md
10
README.md
@ -2,7 +2,7 @@
|
||||
|
||||
This guide describes how to deploy a Kubernetes cluster tailored to my environment using the provided `redbutton.sh` script.
|
||||
|
||||
Just be sure to edit the variables in the `init-deploy.sh` script. I think you can scale this out by adding more hosts and adjusting the for loop but I haven't tried it yet. I needed three machines and that is what I worked with.
|
||||
Just be sure to edit the variables in the `redbutton.sh` script. I think you can scale this out by adding more hosts and adjusting the for loop but I haven't tried it yet. I needed three machines and that is what I worked with.
|
||||
|
||||
## ⚙️ Pre-requisites
|
||||
|
||||
@ -19,10 +19,10 @@ This setup will create a Kubernetes cluster with the following topology and comp
|
||||
- **1 Control Plane Node**
|
||||
- **2 Worker Nodes**
|
||||
- **Calico** as the CNI (Container Network Interface)
|
||||
- **MetalLB** as the cloud load balancer for bare metal services (change the configmap to adapt it to your network)
|
||||
- **Traefik** as the ingress controller on IP 10.50.3.30 (change it in the values.yaml to adapt it to your network)
|
||||
- **Cert-Manager** to manage the internal certificates. Remember to update the API key!
|
||||
- **Longhorn** as the persistent storage provider (change the host to adapt it to your network)
|
||||
- **MetalLB** as the cloud load balancer for bare metal services on your desired range
|
||||
- **Traefik** as the ingress controller on your desired IP
|
||||
- **Cert-Manager** to manage the internal certificates. Remember to set the API Key!
|
||||
- **Longhorn** as the persistent storage provider to your desired hostname
|
||||
|
||||
## 🚀 How to Deploy
|
||||
|
||||
|
Reference in New Issue
Block a user