odo deploy should support creation of Knative:Service

[sspeiche]

Description

As a developer, I'd like a way to have odo deploy to utilize deployment guidance in devfile to create a kn:Service instead of a kubernetes Deployment or OpenShift Deployment config.

Acceptance criteria

• Developer can create a new application component as a Knative Service and match the behavior in OpenShift's web ui.

Possible cli flows

Ability to use odo to deploy as a Knative Service, using deployment guidance in devfile

[kadel]

I think that this is something that should be captured in devfile and than odo will act on that information.
The reason why I think it would be better to captured this in devfile is to make it consistent across all tools. If I have an application that assumes that will be run as Knative Service I don't want to configure odo and again Che to make sure that my apps get deployed correctly. I would just define this in devfile, and then tools should handle it.

[serenamarie125]

Moved out to 2.2 milestone due to dependencies on devfile 2.2

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[dharmit]

/lifecycle frozen

[kadel]

with odo deploy implemented and devfile having support for outer loop. It is fairly straight forward to create a devfile that utilizes KNative Service for outer loop deployment

I've created a simple example https://github.com/kadel/devfile-nodejs-deploy/blob/e42112fe1256ea2a18b93e19f6919f1c5f5513dd/devfile.yaml#L55-L69