h3. Overview

Would be nice as a transformation option to "make a component serverless".  In Topology, if the user selected a DC/D and converted it to serverless"

• As a developer, I want to migrate an existing deployment to serverless
• As a dev, when I migrate my existing deployments I may want to specify additional adv options

Exploration Results

Jamboard from Epic Exploration can be found here

– Update this list after Epic Exploration

1. Tech Preview feature, documentation should be stretch goal
2. Tech Preview feature, enablement should be stretch goal
3. Include in what's new RHD blog
4. Consider for stretch RHD blog

Acceptance Criteria

1. As a developer, I should be able to migrate my existing deployment to a knative service
   1. When migrating, I should be able to specify any advanced options which i'm able to specify upon creating a knative service
   2. When migrating, my initial deployments should not be deleted

Design Artifacts

tbd

Slack Channel

#tmp-odc-serverless

Notes

1. This will be a purely UI oriented solution
2. We are not going to delete Deployments when converting

Previous notes

1. Consider using "Knatify" and "Transform to Knative" service for CTA label
2. Should this be accomplished in the UI or do we need an API to do this work so we can utilize it across the portfolio? Would like a consistent approach used to support this feature in Console, odo and OpenShift Connector. Realistically odo's backlog is large and this wouldn't be prioritized for some time.
3. We had some early experiments around that with a tool called "knatify" put together by one of our engineers - https://github.com/markusthoemmes/knatify