The operator currently utilises the /v2/container/config?action=listen endpoint to consume CRUD events for caches and their configuration so that it can update the k8s resources to reflect the server's state. The plan is to add similar logic for Counters, Proto schemas and other container resources.

Exposing these resources over multiple endpoints that the Operator implementation must create multiple streams to consume, using a go routine per stream.

Exposing all events via a single endpoint will greatly simplify the logic required in the Operator as well as improving the user-experience for Infinispan users.

We could expose this via /v2/container?action=listen. With the stream providing events for resource, config and lifecycle updates e.g. StateTransfer/Rebalancing completion.