Requirement

We have a simple and powerful mechanism with Pipe binding which allow to easily configure existing Kubernetes custom resource which are "addressable". Let's think of Knative resource or Strimzi Kafka, which make it easy to configure without knowing low lever configuration details. We should extend to more useful resources such as:

• Artemis Queue CR
• Service CR CR
• Camel K Integration CR (ie, when it exposes a service)
• Camel K Pipe CR (ie, when it exposes a service)