Dual Ingress (gRPC & HTTP) Doesn't Support GCE Load Balancer #303
Description
Hello!
I'm a Superblocks customer using OPAs to manage admin applications. A few months ago, Superblocks shipped a change to include two ingress objects, one for HTTP and one for gRPC. I have unfortunately not been able to upgrade my OPAs using the new chart because I use GCE Load Balancers, which only support one Ingress per IP, and defines the IP via an annotation kubernetes.io/ingress.global-static-ip-name: superblocks-global-ingress-address. Unfortunately, the Superblocks chart reuses the annotations across the two Ingress.
It looks like the gRPC ingress is separated out to support a hardcoded nginx annotation for a gRPC backend. This annotation is implementation-specific and not required for my GCE load balancers.
I'm hoping that Superblocks could modify the chart so that I can continue using the supported configuration with my GCE load balancers. For example, gRPC and HTTP annotations could be defined separately, or there could be an option to use a single Ingress with separate paths for both gRPC and HTTP backends when the nginx annotation is not required.
Thank you for your help!