Closed themr0c closed 1 year ago
The horizontal and downward arrows make this look a little too much like a flow to me, i.e. I install Podman, the OpenShift Local, then Lima, next I do Podman and Docker, etc. As a user it's also not clear why something like OpenShift Local is in VM and Kubernetes columns and if this means I need to set it up twice or what.
I guess the bottom line is that it's not clear to me what we're showing here, and if it is just meant as a catalog to find things in a particular category, a one-stop shop for all starting points, or something else. As a user, how does this help vs the existing nav or googling what I'm trying to install?
Could we also pick colors from the palette / existing colors from the website so that things match?
OK, make clear that at every column you have the choice between each item in the column
That's already with the colors from the palette as much as we can.
@deboer-tim It is using color values from our palette file, although I think it transforms the colors based on whether or not you're in light or dark mode. I think the dark mode version is more on-brand. I haven't quite fully figured out the theming system yet.
The diagram is missing the option to only install Kubernetes, directly on the virtual machine provided by Lima.
That is, it is not using the container engine (Podman, Docker) but only the container runtime (CRI-O, containerd)
It could even be listed twice as "Lima: k3s" and "Lima: k8s", depending on which installer the user chooses:
https://podman-desktop.io/docs/Installation/creating-a-lima-instance-with-podman-desktop#kubernetes
Even more complete:
I was more thinking to add two boxes in the Kubernetes column, but it's OK to scope them out...
They're covered by the "bring your own kubeconfig" (until they can be provided), for the provider.
Just that your diagram seemed to imply that podman/docker is required for running Kubernetes
With all the feedback received, it's going in a new direction.
New outline:
Sankey diagram does not bring clarity. New attempt with timeline diagram and matrix tables.
To run container workloads, set up at least one container engine.
Podman Desktop does not automatically set up container engine resources that you might not need.
Select a container engine supporting your workload.
Workload | Podman | Docker |
---|---|---|
Rootless containers | yes | no |
Rootful containers | yes | yes |
Compose | yes | yes |
Pods | yes | no |
Podman supports rootless container and pods, in addition to rootful containers and Compose.
Select an execution environment supporting your container engine and your operating system.
Select a Podman execution environment:
Host operating system | Native containers | Podman machine | Lima machine |
---|---|---|---|
Windows | no | yes | no |
macOS | no | yes | yes |
Linux | yes | no | no |
Select a Docker execution environment:
Host operating system | Native containers | Lima machine | Docker Desktop |
---|---|---|---|
Windows | no | no | yes |
macOS | no | yes | yes |
Linux | yes | no | yes |
Setup your container engine.
Podman Desktop assists you to set up Podman and Podman machines on Windows and macOS, and consumes your native Podman, Lima or Docker setup.
(Added the content as a comment for better visualization)
Lima works also on Linux, and will eventually also support Windows (there is an experimental WSL2 driver already)
Podman machine also supports Linux (accelerated by KVM), it is just disabled (not available) in Podman Desktop.
@afbjorklund @jeffmaury Suggestions implemented. Do they work for you?
Thanks for updating, not easy doing these comparisons for constantly updated and "highly political" targets
True :). How many iterations on this pull request, and still learning some details :). Can I count on you to create an issue here to update our docs once Windows support gets stable in Lima?
Sure, I can update the Lima content... And I think Podman will get similar updates, once it supports VMs (Hyper-V) in addition to WSL
I am also looking for feedback from Lima users on Mac, if they prefer the CLI or the GUI* for setting it up? (creating and starting, that is)
Onboarding introduction.
Started as a single diagram, evolved into a compleye onboarding introduction.