vagrant-k3s-metallb

KO | EN

gitlite — search

#javascript #react #android #machine-learning #deep-learning #nodejs #java #windows #kubernetes #vue #pytorch #mcp #openai #open-source

vagrant-k3s-metallb

(★ 12)

k3s using metallb in bpg mode, with a service preserving source IP.

vagrant-k3s-metallb 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Summary

A multi-vm `Vagrantfile` for setting up a k3s cluster using metallb in BGP mode, running a service preserving source IP.

# Usage

```sh
vagrant up
```

# Description

The setup is composed of 5 vms and two private networks.

## client

The client vm is used only to query the service from another network. To test the routing setup by BGP.

* IPs: 
  - 192.168.90.10

# router

The `router` vm connects to 3 networks, the `public_network` which might be used to access the vms from the host.

> The `bridge` name should match the interface being used to access internet on the host.

This vm provides connection between the two private networks:

* k3s-metallb-net 192.168.33.0/24 Used by the nodes as ClusterIPs and by the router on the interface listening where's listening the bgp service.
* client-metallb-net 192.168.90.0/24  Used the `client` vm.

* IPs: 
  - 192.168.90.1
  - 192.168.33.1
  - 192.168.1.200

# flannel setup

Out of the box flannel will not work with vagrant, neither with k3s.

The available `flannel.yml` file requires two modifications to work on this setup:

1. To specify the interface to be used by flannel: `--iface=enp0s8`
2. To replace the default k8s network block (`10.244.0.0/16`) by the one used by k3s: `10.42.0.0/16`

The `kube-flannel.yml` file is provided with the changes required to make k3s work with Vagrant.

The first interface on a vm is on the network which allows vagrant to communicate with and to provide NAT traffic to the guest.

# Troubleshooting

When looking at the logs from k3s, `kubetail` proved to be an interesting tool.

```
vagrant ssh master
```

```sh
curl -sO https://raw.githubusercontent.com/johanhaleby/kubetail/master/kubetail ; chmod 755 kubetail ; sudo mv kubetail /usr/local/bin/
kubetail -l component=speaker -n metallb-system
```

Check the pods from metallb

```
vagrant@node0:~$ kubectl get po -o wide -n metallb-system
```

The speakers pods should be using an IP from the  `192.168.33.x/24` network.

Checking BGP routes on the bird daemon.

```
vagrant ssh router
```

```
sudo birdc
show protocols all
```

Check for `connections refused`, that points to networking issues, double-check all ips are assigned as expected.

Inspecting http traffic

```
tcpdump -i any -s 0 'tcp port http' 
```

# cleanup

```sh
vagrant destroy -f
```

## References:

* https://qiita.com/omatsu32/items/20b337b96595b6320be3
* https://metallb.universe.tf/usage/#local-traffic-policy-1
* https://kubernetes.io/docs/tutorials/services/source-ip/

vagrant-k3s-metallb

vagrant-k3s-metallb 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

vagrant-k3s-metallb

vagrant-k3s-metallb 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README