-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] Podman roadmap to stable #1778
Comments
/area provider/podman For those interested please report the missing features that you find |
/assign |
This looks great! |
I'm in favor of this. |
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: Right now we are pinning 1.9.3, due to the 2.0.x bugs |
I don't think we should worry about windows / Mac for now. We're supporting 2.X in kind 0.9 |
Our issues with podman 2.x was mostly about The podman driver (for minikube) is more or less back now, We are hoping that most of the worst regressions are fixed in |
here we go containers/podman#8143 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
I have added a similar story for minikube, we are hoping for podman v3.... |
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. |
/remove-lifecycle stale |
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:
https://github.com/aojea/kind/actions?query=workflow%3APodman
WIP Podman vs Docker networking: IPv4, IPv6 and Dual Stack containers/podman#7302
The text was updated successfully, but these errors were encountered: