Run `cloud-provider-kind` as a podman container

[see-quick]

Currently, running cloud-provider-kind within a container that utilizes podman.sock is not supported. Implementing this functionality would benefit users operating in Podman environments where only podman.sock is available.

[aojea]

We use the docker-cli as base image, I imagine that is necessary to also pull the podman binary into the image so the cloud-provider-kind can use it

cloud-provider-kind/Dockerfile

Lines 11 to 14 in 56fc897

	# build real cloud-provider-kind image
	FROM docker:25.0-cli
	COPY --from=0 --chown=root:root ./go/src/bin/cloud-provider-kind /bin/cloud-provider-kind
	ENTRYPOINT ["/bin/cloud-provider-kind"]

It also needs documentation and some validation

/help

[k8s-ci-robot]

@aojea:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

Details

In response to this:

We use the docker-cli as base image, I imagine that is necessary to also pull the podman binary into the image so the cloud-provider-kind can use it

cloud-provider-kind/Dockerfile

Lines 11 to 14 in 56fc897

	# build real cloud-provider-kind image
	FROM docker:25.0-cli
	COPY --from=0 --chown=root:root ./go/src/bin/cloud-provider-kind /bin/cloud-provider-kind
	ENTRYPOINT ["/bin/cloud-provider-kind"]

It also needs documentation and some validation

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[manalilatkar]

/assign

[GunaKKIBM]

/assign

[see-quick]

Any update on this @GunaKKIBM?

[GunaKKIBM]

@see-quick , Sorry allow me a day's time. I was away last week. I will share some update by tomorrow.

[BenTheElder]

We might want to consider different images depending on the size.

FWIW I'd recommend running it on the host directly, kind already expects this and cloud-provider-kind is similarly a statically linked single go binary with no additional dependencies vs kind.

[GunaKKIBM]

@see-quick

I am new to using cloud-provider-kind. I needed some clarification on the issue here. I tried running the cloud-provider-kind binary inside a podman machine (on mac), taking a look at the code, cloud-provider-kind has support for all providers (docker, nerdctl and podman) just like kind.

Are you saying, when we try to run a container using podman, and inside the container, we build and run cloud-provider-kind, it doesn't work? Can you please share the steps which gives me better clarity on what's not working and what you expect?

[GunaKKIBM]

@see-quick

Could you please share your thoughts for my question above?

[see-quick]

@see-quick

Could you please share your thoughts for my question above?

Hi, sorry for late response.

a podman machine (on mac)

Well, you can run it like this (when you directly download the binary to the podman machine), but when you try to run registry.k8s.io/cloud-provider-kind/cloud-controller-manager:v0.6.0 , which is only Docker running AFAIK. Check this thread within Kubernetes Slack if you want to get the whole picture :) [1]

[1] - https://kubernetes.slack.com/archives/CEKK1KTN2/p1741169687686129