kosmotron + capd doesn't work at all

[xinity]

hello there,

seems like the capd provider is not working at all,

testing on several ubuntu 22.04 instance:

• locally (using parallels)
• VM on azure

thoroughly followed the official kosmotron documentation.

here are the exact steps i've taken:

• docker network rm kind

• docker network create kind --opt com.docker.network.bridge.enable_ip_masquerade=true this steps doesn't seem to be necessary as by default masquerading is enabled in the kind network

• kind create cluster --config kind-cluster-with-extramounts.yaml (not dual stack but ipv4 only)

• export CLUSTER_TOPOLOGY=true

• clusterctl init --core cluster-api --infrastructure docker

• kubectl apply --server-side=true -f https://docs.k0smotron.io/v1.0.0/install.yaml

copy/paste the yaml available here: https://docs.k0smotron.io/stable/capi-docker/#creating-a-child-cluster

• kubectl apply -f [ the yaml file ]

i always end up this way:

the logs of kuberouter says:

2024-06-28T16:38:19.768428413Z stderr F E0628 16:38:19.768398       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.23.7/tools/cache/reflector.go:167: Failed to watch *v1.Node: failed to list *v1.Node: Get "https://10.96.0.1:443/api/v1/nodes?limit=500&resourceVersion=0": dial tcp 10.96.0.1:443: i/o timeout
2024-06-28T16:38:49.766599155Z stderr F failed to run kube-router: Failed to synchronize cache: 1m0s timeout

[xinity]

@makhov seems like a weird network issue, the default kubernetes service ip isn't reachable.

Weird enough because I can deploy "vanilla" capd clusters without any network issues.

Trying to figure out where the devil lives, but failed so far 😢