killianmuldoon

/remove-lifecycle stale Work is still ongoing - tracked in #6458 to make the UX for this better for CAPI

I think for Mac it would be incredibly difficult to navigate Docker Desktop to try to recreate what the CLI does to get the port mappings, so we're probably left...

I think for Mac it would be incredibly difficult to navigate Docker Desktop to try to recreate what the CLI does to get the port mappings, so we're probably left...

Agreed that this might be a step further than we'd like to go to make the quick start a little easier. It looks to me that Kind is using provider...

The workaround for this for most users is probably just to use `kind` to get the kubeconfig - this is changed in documentation in #7392. I think we can close...

This isn't necessarily a networking error - when the client is timing out like that it means the Cluster isn't contactable. That could be a network error, or it could...

Can you check the status of the Machine objects? Can you see if there are errors in the logs of CAPD?

I'm not sure what the issue is with the haproxy container - I've seen it fail due to resource exhaustion on Linux systems at times. Can you share what resources...

I really think the networking issue is the symptom rather than the cause here. The IP isn't reachable because the container isn't up. The first places I'd look for information...

@umesh168 did you manage to resolve this?