KIND, Podman, WSL2, self-hosted GH Runner about kind HOT 6 CLOSED

Thank you @BenTheElder @tao12345666333

from kind.

I think this has already exceeded the scope that can be covered by support for this project.

As shown in your first screenshot, the KIND cluster is running correctly and can be interacted with through kubectl.

As long as you ensure the following parts, it can meet your expectations:

• KIND's container is running
• The kubeconfig is correct
• Network connectivity is correct

from kind.

It is running and building in the first stage, but can’t connect to it in the second stage. Also I am unable to connect to it on the host, getting the same error. I understand if this is out of scope.

from kind.

GitHub runners are a bit out of scope for us.

AFAICT kind is working as intended and something about the actions execution environment prevents access in subsequent steps.

If you're running things in containers, they need to be on the kind bridge and use the --internal kubeconfig

from kind.

from kind.

I see.

In the abstract, connecting to the kind node from the host or another container is just connecting to a container like podman run -p 127.0.0.1:6443:6443 ..., connecting to this port forward is not really kind specific and debugging WSL2/podman networking is not something we can scale while maintaining the kind project in addition to our other roles.

I would recommend trying a simpler container with port forward to debug the networking situation on the host, while what is behind the port forward is more complex, the port forward / container address itself should not be unusual versus other simpler containers and podman / the host are responsible for implementing this part.

from kind.