Many buses are infrastructure that should be managed by an operations team. For example, the Kafka bus needs to connect to a pre-provisioned Kafka broker.
Expected Behavior
Buses should often be provisioned by a cluster operator. Channels and Subscriptions are created by developers to consume the bus's capabilities. Likewise, resources in different namespaces should be able to consume the same bus without needing to provision the same bus within each namespace.
Actual Behavior
Bus, Channel and Subscription are all namespaced resources, and do not work outside of a single namespace. Likewise, the developer must provision and manage the bus.
Additional Info
We may want developers to be able to create simple buses (like StubBus) without bugging an operator. In that case, we can introduce both a ClusterBus and Bus resources. In the future, we may also want to limit which namespaces have access to a cluster wide bus.
Refs slack and #88
/kind discussion
cc @vaikas-google @evankanderson @grantr
Many buses are infrastructure that should be managed by an operations team. For example, the Kafka bus needs to connect to a pre-provisioned Kafka broker.
Expected Behavior
Buses should often be provisioned by a cluster operator. Channels and Subscriptions are created by developers to consume the bus's capabilities. Likewise, resources in different namespaces should be able to consume the same bus without needing to provision the same bus within each namespace.
Actual Behavior
Bus, Channel and Subscription are all namespaced resources, and do not work outside of a single namespace. Likewise, the developer must provision and manage the bus.
Additional Info
We may want developers to be able to create simple buses (like StubBus) without bugging an operator. In that case, we can introduce both a
ClusterBusandBusresources. In the future, we may also want to limit which namespaces have access to a cluster wide bus.Refs slack and #88
/kind discussion
cc @vaikas-google @evankanderson @grantr