Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/rgl/rancher-ubuntu-vagrant
rancher ha wrapped in a vagrant environment
https://github.com/rgl/rancher-ubuntu-vagrant
kubernetes rancher vagrant
Last synced: 10 days ago
JSON representation
rancher ha wrapped in a vagrant environment
- Host: GitHub
- URL: https://github.com/rgl/rancher-ubuntu-vagrant
- Owner: rgl
- Created: 2019-10-05T11:51:50.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2021-09-04T15:57:53.000Z (over 3 years ago)
- Last Synced: 2024-10-04T18:41:27.879Z (3 months ago)
- Topics: kubernetes, rancher, vagrant
- Language: Shell
- Size: 203 KB
- Stars: 2
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# About
This is a [ha rancher](https://rancher.com/docs/rancher/v2.x/en/installation/ha/) environment.
For a non-ha environment see the [rgl/rancher-single-node-ubuntu-vagrant](https://github.com/rgl/rancher-single-node-ubuntu-vagrant) repository.
## Usage
Install the [ubuntu-20.04-amd64](https://github.com/rgl/ubuntu-vagrant) box.
Launch the environment:
```bash
vagrant up --no-destroy-on-error --provider=libvirt # or --provider=virtualbox
```
Configure your host DNS resolver to delegate the `rancher.test` domain to the `pandora` machine like described in this document. Or add the environment hosts to your machine `hosts` file:
```plain
10.10.0.2 pandora.rancher.test
10.10.0.3 server.rancher.test
10.10.0.5 server1.rancher.test
10.10.0.6 server2.rancher.test
10.10.0.7 server3.rancher.test
```
Access the rancher server at https://server.rancher.test and login with the default `admin` username and password.
The rancher load balancer statistics are at http://server.rancher.test:9000.
The docker registry is at https://pandora.rancher.test:5000.
The apt-cacher is at http://pandora.rancher.test:3142/acng-report.html (click the "Count Data" button to see the cache statistics).
You can access the example cluster from the host with, e.g.:
```bash
export KUBECONFIG=$PWD/shared/admin.conf
kubectl version --short
kubectl cluster-info
kubectl api-versions
kubectl api-resources -o wide
kubectl get namespaces
kubectl get all --all-namespaces -o wide
kubectl get events --all-namespaces --sort-by=.metadata.creationTimestamp
```
## DNS
Make sure that all of the following commands return the IP address of our `pandora` dns server:
```bash
docker run -it --rm --name test debian:buster-slim cat /etc/resolv.conf # => nameserver 10.10.0.2
kubectl --namespace ingress-nginx \
exec \
$(kubectl --namespace ingress-nginx get pods -l app=ingress-nginx -o name) \
-- \
cat /etc/resolv.conf # => nameserver 10.10.0.2
kubectl --namespace ingress-nginx \
exec \
$(kubectl --namespace ingress-nginx get pods -l app=ingress-nginx -o name) \
-- \
cat /etc/nginx/nginx.conf | grep resolver # => resolver 10.10.0.2 valid=30s;
```
## Host DNS resolver
To delegate the `rancher.test` zone to the kubernetes managed external dns server (running in pandora) you need to configure your system to delegate that DNS zone to the pandora DNS server, for that, you can configure your system to only use dnsmasq.
For example, on my Ubuntu 20.04 Desktop, I have uninstalled `resolvconf`, disabled `NetworkManager`, and manually configured the network interfaces:
```bash
sudo su -l
for n in NetworkManager NetworkManager-wait-online NetworkManager-dispatcher network-manager; do
systemctl mask --now $n
done
apt-get remove --purge resolvconf
cat >/etc/network/interfaces <<'EOF'
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto enp3s0
iface enp3s0 inet dhcp
EOF
reboot
```
Then, replaced `systemd-resolved` with `dnsmasq`:
```bash
sudo su -l
apt-get install -y --no-install-recommends dnsutils dnsmasq
systemctl mask --now systemd-resolved
cat >/etc/dnsmasq.d/local.conf </etc/resolv.conf <