odo dev: react to changes as soon as possible

[rm3l]

/kind user-story

User Story

• As an odo user
• I want to make changes to my source code and Devfile (or even external cluster resources)
• So that the changes are considered as soon as possible

Acceptance Criteria

• It should handle Devfile changes when a Pod is in an Error state
• It should not wait for a specific state in the reconcile loop
• It should watch for all interesting resources (Deployment, ServiceBindings, ...) permanently, i.e. as long as odo dev is running
• It should notify users of the current application state
• If odo dev is running with the no-watch flag, it should not watch for files but still continue to watch cluster resources
• It should wait until the container is listening on the intended port before stating the application is ready (see odo dev port forward timeouts if app is not ready #5877) => tracked in odo dev port forward timeouts if app is not ready #5877

Notes

• Use new approach based on reconcile loop POC: https://github.com/feloy/odo-dev-controller-poc
• Manual trigger will be done in manually trigger file sync in odo dev #5634

Links

• Related Epic (mandatory): [Epic] Address user feedback #5848
• Parent User Story: odo dev needs to handle changes in devfile.yaml #5728

/kind user-story

[dharmit]

• It should watch for all interesting resources (Deployment, ServiceBindings, ...) permanently, i.e. as long as odo dev is running

@feloy I know we discussed this in the grooming call, but I can't recall what it would mean to "watch" for all resources. Can that be elaborated here?

[feloy]

Watch means using the Watch operation of the Kubernetes API, to run a non terminating HTTP request and get events every time a resource we are watching is created / modified / deleted.

We are using this Watch operation in odo, for example here (https://github.com/redhat-developer/odo/blob/main/pkg/kclient/projects.go#L72) to watch for projects resources, and wait for a DELETE event on the specific resource we are waiting to be deleted.

[rm3l]

/close

Last point (It should wait until the container is listening on the intended port before stating the application is ready) will be addressed as part of #5877

[openshift-ci]

@rm3l: Closing this issue.

In response to this:

/close

Last point (It should wait until the container is listening on the intended port before stating the application is ready) will be addressed as part of #5877

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.