Support dedicatedPod field on container components

[rm3l]

/kind feature
/area devfile-spec

Which functionality do you think we should add?

dedicatedPod seems to be ignored currently by odo. Per the Devfile spec, it is supposed to allow running a container in its own Pod.

This seems to be a limitation in the Devfile library: devfile/api#670. So I guess it must be fixed in the library, then pulled into odo.

Why is this needed?

To improve our coverage of the Devfile spec

I guess supporting this might have other implications like:

• port-forwarding: make sure to port-forward to the right pod
• Limitations on unique port values might no longer make sense in some cases, e.g., having the same port defined in different container components is okay, as long as they are in different pods.
• Impact on Podman
• ...

Related

• Epic: [Epic] Improve devfile spec support in odo #5834

[rm3l]

Grooming (2023-06-01)

Check if it is supported in DevSpaces (1 story point for researching).
Priority will depend on whether it is supported there or not. If it is, we'll consider supporting it here as well (we'll groom it later on). But if it is not, we'll lower the priority, unless someone really needs this.

[feloy]

dedicatedPod is not supported in DevSpaces.
Tested with project https://github.com/feloy/devspaces-demo

[rm3l]

/priority Low

[rm3l]

dedicatedPod is not supported in DevSpaces. Tested with project feloy/devspaces-demo

Thanks for the research, @feloy! Based on that information, I've reduced the priority of this issue and will add it for future grooming consideration if we decide to work on it later.

/lifecycle frozen