If folks are creating a Deployment and a Service to consume HTTP endpoints, it might be neater to add the Subscription metadata onto the Service itself via labels/annotations?
maybe just including the Subscription resource along with the app that creates the Service may be simpler really; it'd certainly make the tooling easier.
If folks are creating a Deployment and a Service to consume HTTP endpoints, it might be neater to add the Subscription metadata onto the Service itself via labels/annotations?
See https://github.com/fabric8io/fabric8-ipaas/issues/259
Then as a Service developer, you expose a HTTP endpoint then you can also subscribe that service to some other endpoint (kafka or whatever) as well?