Service discovery mechanism for hocus workspace about hocus HOT 3 CLOSED

Seems like I can use telepresence to work around it. Closing this issue.

from hocus.

Sorry for the late response. We currently have no plans to allow workspaces to communicate with each other. You may use Tailscale if you would like to work around that. I don't quite understand the use case you are proposing with connecting to Kubernetes. Could you give an example of a workflow you have in mind? Why would you want Hocus to integrate with the deployment mechanisms offered by Kubernetes?

from hocus.

Thank you for your response. In a microservices architecture, services are often split across multiple projects and workspaces. Debugging such an architecture can be challenging without proper communication between services.

For instance, consider two projects, A and B, which are two services that need to communicate with each other to implement a function. In Hocus, these projects have their own workspaces. Without a mechanism that allows workspaces to communicate with each other, debugging the application during development would be difficult.

Okteto is an excellent tool that facilitates development directly in a Kubernetes cluster. Each development environment runs in a Pod, and a corresponding Service is created as well. This allows for communication between services across projects by using exposed service names in Kubernetes during development.

However, it would be great if Hocus could provide a similar service discovery and communication mechanism.

from hocus.