Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/rgl/rke2-vagrant
A rke2 kubernetes cluster playground wrapped in a Vagrant environment
https://github.com/rgl/rke2-vagrant
k8s kubernetes rke2 vagrant
Last synced: 2 months ago
JSON representation
A rke2 kubernetes cluster playground wrapped in a Vagrant environment
- Host: GitHub
- URL: https://github.com/rgl/rke2-vagrant
- Owner: rgl
- Created: 2021-09-10T21:54:06.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2023-12-08T17:24:50.000Z (about 1 year ago)
- Last Synced: 2024-10-03T18:52:25.449Z (3 months ago)
- Topics: k8s, kubernetes, rke2, vagrant
- Language: Shell
- Homepage:
- Size: 56.6 KB
- Stars: 8
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# About
This is a [rke2](https://github.com/rancher/rke2) kubernetes cluster playground wrapped in a Vagrant environment.
# Usage
Configure your hosts file with:
```
10.11.0.100 server.rke2.test
10.11.0.201 example-app.rke2.test
```
Install the base [Ubuntu 22.04 vagrant box](https://github.com/rgl/ubuntu-vagrant).
Install the base [Windows 2022 vagrant box](https://github.com/rgl/windows-vagrant).
Launch the environment:
```bash
time vagrant up --no-destroy-on-error --no-tty --provider=libvirt
```
**NB** The server nodes (e.g. `server1`) are [tainted](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) to prevent them from executing non control-plane workloads. That kind of workload is executed in the agent nodes (e.g. `agent1`).
Access the cluster from the host:
```bash
export KUBECONFIG=$PWD/tmp/admin.conf
kubectl cluster-info
kubectl get nodes -o wide
```
Access the example application and notice the `GOOS` property value
round-robin between `linux` and `windows`:
http://example-app.rke2.test
## Kubernetes API
Access the Kubernetes API at:
https://server.rke2.test:6443
**NB** You must use the client certificate that is inside the `tmp/admin.conf`,
`tmp/*.pem`, or `/etc/rancher/rke2/rke2.yaml` (inside the `server1` machine)
file.
Access the Kubernetes API using the client certificate with httpie:
```bash
http \
--verify tmp/default-ca-crt.pem \
--cert tmp/default-crt.pem \
--cert-key tmp/default-key.pem \
https://server.rke2.test:6443
```
Or with curl:
```bash
curl \
--cacert tmp/default-ca-crt.pem \
--cert tmp/default-crt.pem \
--key tmp/default-key.pem \
https://server.rke2.test:6443
```
## K9s Dashboard
The [K9s](https://github.com/derailed/k9s) console UI dashboard is also
installed in the server node. You can access it by running:
```bash
vagrant ssh server1
sudo su -l
k9s
```
# References
* [rancher/rke2 repository](https://github.com/rancher/rke2).
* [rancher/windows repository](https://github.com/rancher/windows).
* [Windows and Linux Cluster Feature Parity](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/use-windows-clusters/windows-linux-cluster-feature-parity).
* [Windows Operational Readiness](https://github.com/kubernetes-sigs/windows-operational-readiness).