k8s/baseline
k8s/baseline
3
0
Fork 0
Code Issues 1 Pull requests Releases Activity

DOC: update README

Browse source 
* merge INSTALL.md into README
* remove unused section
This commit is contained in:
Sebastian Mark 2022-04-10 11:02:21 +02:00
parent f190b4afde
commit d0af285235
2 changed files with 10 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
INSTALL.md
View file

@ -1,12 +0,0 @@
# Install k3s single master node
```
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--disable traefik" sh -s -
```
Copy `/etc/rancher/k3s/k3s.yaml` on your machine located outside the cluster as
`~/.kube/config`.
Then:
* replace "127.0.0.1" with the IP or name of your K3s server.
* rename cluster/context/auth (Hint: `s/default/myserver/g`)

15
README.md
View file

@ -10,13 +10,18 @@ Run `kubectl apply -f init.yml` to install:
* [keel](https://keel.sh) * [keel](https://keel.sh)
* [reloader](https://github.com/stakater/Reloader) * [reloader](https://github.com/stakater/Reloader)
## Installation (k3s + baseline)
`ansible-playbook -i <host|ip>, install.yml`
## Installation (baseline only)
make sure kubectl is configure to reach the destination cluster, then:
`kubectl apply -f init.yml`
## Notes ## Notes
### ingress-nginx servicemonitor
For unknown reasons the servicemonitor is not create on helm install and therefore no metrics will be scraped by prometheus.
Use `helm upgrade -n ingress-nginx ingress-nginx ingress-nginx/ingress-nginx` to force an update of t the release.
### Linode ### Linode
PROXY protocol needs to be enabled for ingress-nginx to see the clients IP in ingress log. PROXY protocol needs to be enabled for ingress-nginx to see the clients IP in ingress log.