homelab/k3s-ansible
3
0
Fork 0
forked from tim/k3s-ansible
Code Pull Requests Activity

Pick kube-vip interface automatically by default (#238)

Browse Source 
* Pick kube-vip interface automatically by default

* molecule: Fix ipv6 scenario

* Choose a more restrictive molecule timeout in CI
This commit is contained in:
Simon Leiner
2023-02-20 05:08:36 +01:00
committed by GitHub
parent 65bbc8e2ac
commit 7bc198ab26
4 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
molecule/ipv6/overrides.yml
View File

@@ -7,6 +7,11 @@
# See: https://github.com/flannel-io/flannel/blob/67d603aaf45ef80f5dd39f43714fc5e6f8a637eb/Documentation/troubleshooting.md#Vagrant # noqa yaml[line-length]
flannel_iface: eth1
# In this scenario, we have multiple interfaces that the VIP could be
# broadcasted on. Since we have assigned a dedicated private network
# here, let's make sure that it is used.
kube_vip_iface: eth1
# The test VMs might be a bit slow, so we give them more time to join the cluster:
retry_count: 45