odo dev with podman pod (create pod and sync files)

[feloy]

/kind user-story

User Story

As a user I want to run odo dev with --run-on=podman/cluster flag So that I can choose to execute the component pod on Podman or on Kubernetes

Acceptance Criteria

• odo dev should accept a --run-on flag, with accepted values cluster (default) and podman
• --run-on flag should be experimental (see Experimental mode #6150)
• odo dev in cluster mode should behave as odo dev

odo dev --run-on=podman

• should work without any Kubernetes config
• should support devfiles from Registry (Support devfile volumes during dev on podman #6330)
• should deploy a Pod using podman CLI
• [podman] Expose the ports using the hostPort flag in the Ports of the container #6333
• should sync the local files to the Pod
• should execute the build then run commands
• should cleanup resources then exit when Ctrl-C is pressed
• should not watch for files changes nor devfile changes

Links

• Related Epic (mandatory): [POC] odo without kubernetes cluster / odo on podman #5865

/kind user-story

[elsony]

Exposing as part of the --run-on flag is useful if someone wants to switch between the two modes. Have we considered also putting it as part of the preference so that the user doesn't have to specify that on every odo dev or odo deploy command?

[kadel]

Exposing as part of the --run-on flag is useful if someone wants to switch between the two modes. Have we considered also putting it as part of the preference so that the user doesn't have to specify that on every odo dev or odo deploy command?

That makes sense. We can add this. But it is something that we should consider only after we have a more solid implementation and it is ready to be moved out of experimental mode.

[feloy]

Reopening as some Devfiles (the ones declaring volumes) are not supported

Also, ports should be tested before to be used, to be able to deploy several components at the same time

[rm3l]

Exposing as part of the --run-on flag is useful if someone wants to switch between the two modes. Have we considered also putting it as part of the preference so that the user doesn't have to specify that on every odo dev or odo deploy command?

That makes sense. We can add this. But it is something that we should consider only after we have a more solid implementation and it is ready to be moved out of experimental mode.

I've created a separate issue to keep track of this point: #6331

[rm3l]

As discussed during standup, I'm closing this issue as completed (so it can be visible as such in the v3.3.0 milestone).

Newly added items will be tracked as separate issues:

• Support devfile volumes during dev on podman #6330 (so as to support Devfiles from default registry)
• [podman] Expose the ports using the hostPort flag in the Ports of the container #6333

/close

[openshift-ci]

@rm3l: Closing this issue.

In response to this:

As discussed during standup, I'm closing this issue as complete (so it can be visible as such in the v3.3.0 milestone).
Newly added items will be tracked as separate issues:

• Support devfile volumes during dev on podman #6330 (so as to support Devfiles from default registry)
• [podman] Expose the ports using the hostPort flag in the Ports of the container #6333

/close

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/test-infra repository.