[EPIC] Podman roadmap to stable

[aojea]

Podman roadmap to stable

Currently, Podman provider is set as Experimental, mainly because of subtle differences with Docker that breaks some of the features.

To fix this, KIND implements an interface, so providers can diverge in their implementation maintaining its compatibility at the user level.

In order to move to stable the provider it has to have exactly the same capabilities that the Docker provider.

These are the work items I have identified:

• Implement CI. This runs every night from the KIND master branch testing IPv4, IPv6 single and multinode clusters with HA.
  https://github.com/aojea/kind/actions?query=workflow%3APodman
• Podman networking, this is a topic where podman deviates completely from docker, it's a long history, libnetwork vs CNI. Since 0.8.0 KIND moved to their own bridge, this is missing in podman yet, assign @aojea
  WIP Podman vs Docker networking: IPv4, IPv6 and Dual Stack containers/podman#7302
• Load docker images, this needs further discussion Podman load docker images #1766
• Windows, Mac support (I do not know if this is even possible 😅 )

[aojea]

/area provider/podman
/cc @amwat

For those interested please report the missing features that you find

[aojea]

/assign

[amwat]

This looks great!
Also we should definitely try to see if we can get those github actions running upstream.
thoughts @BenTheElder ?

[BenTheElder]

I'm in favor of this.

[afbjorklund]

Windows, Mac support (I do not know if this is even possible)

It is possible, but you would have to manage the VM yourself since podman only supports a "remote" and not a integrated solution

There are also lots of question marks when it comes to port mapping and such, so thinking of dropping the feature from minikube:

kubernetes/minikube#8003

Right now we are pinning 1.9.3, due to the 2.0.x bugs

[BenTheElder]

I don't think we should worry about windows / Mac for now.

We're supporting 2.X in kind 0.9

[afbjorklund]

Our issues with podman 2.x was mostly about podman-remote

The podman driver (for minikube) is more or less back now,
but we will probably support both of them for a while (2020)

We are hoping that most of the worst regressions are fixed in 2.1 2.2

[aojea]

here we go containers/podman#8143

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[aojea]

/remove-lifecycle stale

[afbjorklund]

I have added a similar story for minikube, we are hoping for podman v3....

kubernetes/minikube#10237

[BenTheElder]

I expect revamped image loading to land in v0.11.0 (just started the cycle for that), I'm not sure we should block on windows / mac support.

We also have some limited CI for podman now, which is good.

[aojea]

/remove-lifecycle stale