Skip to content

Commit

Permalink
docs/Troubleshooting: add calico ipvs interface detection issue (#162)
Browse files Browse the repository at this point in the history
Co-authored-by: Felix Wischke (65278) <[email protected]>
  • Loading branch information
65278 and Felix Wischke (65278) authored Apr 2, 2024
1 parent 2afcf64 commit 9007e3e
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/Troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,3 +63,7 @@ or others, please check the image tag of the `capi-controller-manager` Deploymen
kubectl get deployment/capi-controller-manager -o yaml | yq '.spec.template.spec.containers[].image'
```
If your capi-controller is too new, you can pass a `--core cluster-api:v1.6.1` during `clusterctl init`, to force an older version. By default it installs the latest version from the [kubernetes-sigs/cluster-api](https://github.com/kubernetes-sigs/cluster-api) project.

## Calico fails in IPVS mode with loadBalancers to expose services
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).

0 comments on commit 9007e3e

Please sign in to comment.