coredns updates with AWS user stuff
This commit is contained in:
78
README.md
78
README.md
@@ -21,7 +21,11 @@ curl -sfL https://get.k3s.io | sh -s - \
|
||||
"--disable" \
|
||||
"traefik" \
|
||||
"--disable" \
|
||||
"local-storage"
|
||||
"local-storage" \
|
||||
"--disable" \
|
||||
"coredns" \
|
||||
"--cluster-dns" \
|
||||
"10.43.0.10"
|
||||
```
|
||||
|
||||
Now you can change the ownership of (and copy) the k3s.yaml file:
|
||||
@@ -41,6 +45,27 @@ We're using SQLite (because it's all we really need). The db is stored at
|
||||
and restore it by copying it back. Note, you must also copy`/var/lib/rancher/k3s/server/token`
|
||||
and use the contents as the token when restoring the backup as data is encrypted with that token.
|
||||
|
||||
### CoreDNS
|
||||
|
||||
We'll use our own coredns server so we can add custom hosts. This prevents the server from collapsing
|
||||
if the internet drops out (something that apparently happens quite frequently)
|
||||
|
||||
```bash
|
||||
helm repo add coredns https://coredns.github.io/helm
|
||||
helm repo update
|
||||
helm upgrade --install \
|
||||
--namespace=kube-system \
|
||||
--values coredns-values.yaml \
|
||||
coredns \
|
||||
coredns/coredns
|
||||
```
|
||||
|
||||
You can test your dns config with
|
||||
|
||||
```bash
|
||||
kubectl run -it --rm --restart=Never --image=infoblox/dnstools:latest dnstools
|
||||
```
|
||||
|
||||
### Nginx Ingress
|
||||
|
||||
Now we need an ingress solution (preferably with certs for https). We'll be using nginx since
|
||||
@@ -135,22 +160,6 @@ And now you can install the drivers:
|
||||
helm repo add democratic-csi https://democratic-csi.github.io/charts/
|
||||
helm repo update
|
||||
|
||||
# enc0 bulk storage (nfs)
|
||||
helm upgrade \
|
||||
--install \
|
||||
--values truenas-nfs-enc0.yaml \
|
||||
--namespace democratic-csi \
|
||||
--create-namespace \
|
||||
zfs-nfs-enc0 democratic-csi/democratic-csi
|
||||
|
||||
# enc1 fast storage (nfs)
|
||||
helm upgrade \
|
||||
--install \
|
||||
--values truenas-nfs-enc1.yaml \
|
||||
--namespace democratic-csi \
|
||||
--create-namespace \
|
||||
zfs-nfs-enc1 democratic-csi/democratic-csi
|
||||
|
||||
# enc0 bulk storage (iscsi)
|
||||
helm upgrade \
|
||||
--install \
|
||||
@@ -159,7 +168,7 @@ helm upgrade \
|
||||
--create-namespace \
|
||||
zfs-iscsi-enc0 democratic-csi/democratic-csi
|
||||
|
||||
# enc1 bulk storage (iscsi)
|
||||
# enc1 fast storage (iscsi)
|
||||
helm upgrade \
|
||||
--install \
|
||||
--values truenas-iscsi-enc1.yaml \
|
||||
@@ -174,6 +183,27 @@ You can test that things worked with:
|
||||
kubectl apply -f democratic-csi-pvc-test.yaml
|
||||
```
|
||||
|
||||
### Dashboard
|
||||
|
||||
Create the dashboard and an admin user with:
|
||||
|
||||
```bash
|
||||
helm upgrade \
|
||||
--install \
|
||||
--namespace kubernetes-dashboard \
|
||||
--create-namespace \
|
||||
dashboard-user ./helm/dashboard-user
|
||||
|
||||
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml
|
||||
```
|
||||
|
||||
Then login with the following:
|
||||
|
||||
```bash
|
||||
kubectl -n kubernetes-dashboard create token admin-user
|
||||
kubectl proxy
|
||||
```
|
||||
|
||||
### Nextcloud
|
||||
|
||||
The first chart we'll deploy is nextcloud.
|
||||
@@ -208,6 +238,18 @@ helm upgrade --install \
|
||||
--create-namespace
|
||||
```
|
||||
|
||||
### Minecraft
|
||||
|
||||
Minecraft is available through the custom helm chart (including a server downloader)
|
||||
|
||||
```bash
|
||||
helm upgrade --install \
|
||||
nimcraft \
|
||||
./helm/minecraft \
|
||||
--namespace nimcraft \
|
||||
--create-namespace
|
||||
```
|
||||
|
||||
### Troubleshooting
|
||||
|
||||
Deleting a stuck namespace
|
||||
|
||||
Reference in New Issue
Block a user