Antonio Ojea

/ok-to-test /lgtm /approve

Interesting ... can you list what containers are actually running ? I think it is something as `podman ps -a` and the networks `podman network ls`? any reason to run...

> I had a similar issue and in _my case_ it was caused by `cloud-provider-kind` [using an unqualified image name](https://github.com/kubernetes-sigs/cloud-provider-kind/blob/827fdb16eda5d85eb055a7cad9ed2c1a14a415ae/pkg/loadbalancer/proxy.go#L24) for the `envoyproxy/envoy` image and podman on my system not...

> Sorry for absence. I confirm that error goes away after making alias in shortnames.conf no worries, so I think we can close as this will be fixed by https://github.com/kubernetes-sigs/cloud-provider-kind/pull/124

/ok-to-test /lgtm /approve

This seems a good first issue , we just need to validate before starts, I would say here after the flag parsing https://github.com/kubernetes-sigs/cloud-provider-kind/blob/827fdb16eda5d85eb055a7cad9ed2c1a14a415ae/cmd/app.go#L40-L43 if the process has enough privileges ```...

Fixes by https://github.com/kubernetes-sigs/cloud-provider-kind/pull/128 Thanks @zzzk1

I start to see more users preferring the containerized approach https://github.com/kubernetes-sigs/cloud-provider-kind/pull/125 so it may not be a bad idea

@kranurag7 we can start documenting it and provide some examples, feel free to submit a PR

Added a postsubmit job that updates the images for each commit https://console.cloud.google.com/gcr/images/k8s-staging-kind/GLOBAL/cloud-provider-kind ``` docker pull gcr.io/k8s-staging-kind/cloud-provider-kind:v20240902-781210e ```