Clowder's dependency resolution and endpoint injection is very helpful for wiring services together. However, it was built with the assumption of public/private endpoints only. This becomes problematic when ClowdApps want to expose / consume grpc.

These problems are clearly demonstrated by this class (see the comments): https://github.com/RedHatInsights/notifications-backend/blob/master/backend/src/main/java/com/redhat/cloud/notifications/config/KesselConfigInterceptor.java

Acceptance criteria:

• As a ClowdApp serving grpc API, I can specify that in the ClowdApp definition so that it can be discovered by other services
• As a ClowdApp depending on another ClowdApp that exposes an grpc API, I can discover the host (without incorrect scheme), port and protocol via the endpoints section of cdappconfig.json