Allow configuration of additional ingresses for gRPC

[alee792]

The current templates only allow for a single ingress keyed off of service.port, which defaults to the HTTP server. Practically, this means that ingress cannot be enabled for both HTTP and gRPC. The templates could be modified to create multiple ingress objects, and potentially allow for the injection of different backends for different rules.

[jon-whit]

@alee792 thanks for the issue. For the sake of getting a chart out more quickly, we chose to prioritize the HTTP endpoint integration first, but we can look into a gRPC ingress configuration option as well. It's hard to cater to a single ingress approach though, since different operators will have different infrastructure requirements etc..