Dominik Tornow

I would like to be able to discover Service Mesh Instances as well as the Services and Workloads the Service Mesh Instances know about on an SMI-level. Service Mesh Hub...

> I assume by "service mesh instances" you're interested in knowing what's been installed on the cluster? Yes. For example, I can install [two Istio instances on the same cluster](https://istio.io/blog/2018/soft-multitenancy/)....

> Hmm, services are going to be extremely hard as a single service can have multiple meshes behind it. At first glance, I don't expect much trouble here: I two...

Hey Andrey, good timing, I just published the blog post a few hours ago :) https://blog.resonatehq.io/deterministic-simulation-testing

- Yes, I am encouraging generic (web)hooks, open for discussion are hooks both on API calls as well Commands within RespondWorkflowTaskCompleted API calls. - Ideally hooks can be added to...

While there is a wide range of possibilities, I would advocate for: Admission Controller Workflows are registered with the Temporal Cluster, probably per (namespace, workflow type, workflow queue) and (namespace,...

Absolutely possible that workflows are not the right primitive here! Could be webhooks, could be WebAssembly hooks, could be all three.

+1

A few suggestions: # Monitors Make `Monitor` an interface with a method - `apply(event Event)` - `status() []error` Source internal/announcements/monitor.go # Announcement Extend the `Announcement` interface with a method -...

The [network](https://github.com/resonatehq/resonate/blob/7935e1cae3c90e04152d23f2170acdb101a73946/internal/kernel/t_aio/network.go#L22) is a good candidate to add a first announcement https://github.com/resonatehq/resonate/blob/7935e1cae3c90e04152d23f2170acdb101a73946/internal/kernel/t_aio/network.go#L22