Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: document ipv6 only cluster kube-vip version #172

Merged
merged 1 commit into from
Apr 16, 2024
+22 −1
Merged

docs: document ipv6 only cluster kube-vip version #172

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion docs/Troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,6 @@ If your capi-controller is too new, you can pass a `--core cluster-api:v1.6.1` d
Calico unfortunately does not test connectivity when it choses a node ip to use for IPVS communication.
This can be altered manually. More on this topic in [Calicos documentation](https://docs.tigera.io/calico/latest/networking/ipam/ip-autodetection#autodetection-methods).


## Machine deletion deadlock
Sometimes machines do not delete because some resource needs to be reconciled before
deletion can happen, but these resources can not reconcile (for example nodes may not drain).
Expand All @@ -88,3 +87,16 @@ The image builder uses `PROXMOX_USERNAME` as the token name and `PROXMOX_TOKEN`
the token name and `PROXMOX_SECRET` as the token's secret UUID.
The CAPMOX way of implementing authentication is closer to the [Proxmox API Token Documentation](https://pve.proxmox.com/wiki/Proxmox_VE_API#api_tokens),
therefore this pitfall will likely keep on existing.

## IPv6 only cluster, kube-vip fails with "unable to detect default interface"
Older versions of `kube-vip` do not consider the IPv6 routing table and therefore IPv6 interface detection fails.
Update `kube-vip` to version `0.7.2`.

Example log:
```
time="2024-03-14T11:48:58Z" level=info msg="Starting kube-vip.io [v0.5.10]"
time="2024-03-14T11:48:58Z" level=info msg="namespace [kube-system], Mode: [ARP], Features(s): Control Plane:[true], Services:[false]"
time="2024-03-14T11:48:58Z" level=info msg="No interface is specified for VIP in config, auto-detecting default Interface"
....
time="2024-03-14T11:52:30Z" level=fatal msg="unable to detect default interface -> [Unable to find default route]"
```
9 changes: 9 additions & 0 deletions docs/advanced-setups.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,15 @@ export IPV6_PREFIX=64
export IPV6_GATEWAY="2001:db8:1::1"
```

If you're using cilium, be aware that cilium's helm chart requires `ipv6.enabled=true` to actually support IPv6 pod- and service networks.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy & paste error? This one seems to be double :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's relevant to both sections, and I didn't know how to organize it so there's on redundancy. Suggestions welcome.


## IPv6 only cluster

Clusters without IPv4 are possible, but require kube-vip to be newer than 0.7.1 (version 0.7.0 probably works, but we did not test it).

If you're using cilium, be aware that Cilium's helm chart requires `ipv6.enabled=true` to actually support IPv6 pod- and service networks.


#### Generate a Cluster

```bash
Expand Down
Loading