Support for knative services

[dsyer]

When an application is deployed by Knative, the deployment (as in deployments.apps) is auto-generated. You can easily figure out its name and put it in okteto.yaml as the name of the app, and Okteto will happily create a new deployment and sync your files and all the lovely stuff it does. But it competes with the Knative controller to update the deployment. Knative will notice that Okteto has deleted the deployment and replace it, so you end up with 2 deployments, and only one of them is routed to by the Knative service, which is what the rest of your app depends on using.

It's possible that all Okteto would need to do would be to replace the Knative service instead of the deployment, which would probably end up being a very similar operation.

[pchico83]

Hi @dsyer , this is in fact a very interesting use case!
How are you using knative with okteto? Looking forward to knowing more about your use case.
I haven't used knative before, but I guess a knative service is a similar controller to a statefulset, for example. If that's the case, we have an interface for deployments/statefulsets that could be used to support knative.

[dsyer]

How am I using it? Well not using really, just attempting to use it - via VSCode as it happens, but probably it would be the same for CLI. It sort of works if you point okteto at the generated deployment (as I described), but not really. It would be nice if that interface was implemented for knative.

[github-actions]

This issue is stale because it has been open for 60 days with no activity. Comment on this issue or it will be closed in 7 days

[dsyer]

Definitely not stale