can i use envoy service type LoadBalancer with Ingress resources instead of HttpRoute?

[Babbili]

is there a possibility that i can use envoy-default service type LoadBalancer with Ingress resources instead of HttpRoute , just like in option#1 project Contour which uses Envoy proxy

## Envoy Gateway ##
kubectl -n envoy-gateway-system get all
NAME                                             READY   STATUS    RESTARTS   AGE
pod/envoy-default-eg-e41e7b31-686d67777f-fjplv   2/2     Running   0          27m
pod/envoy-gateway-5d5757c69-rpbt6                1/1     Running   0          32m

NAME                                TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                         AGE
service/envoy-default-eg-e41e7b31   LoadBalancer   10.96.96.128    172.17.0.0    80:32313/TCP                    27m
service/envoy-gateway               ClusterIP      10.96.217.172   <none>        18000/TCP,18001/TCP,19001/TCP   32m

NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/envoy-default-eg-e41e7b31   1/1     1            1           27m
deployment.apps/envoy-gateway               1/1     1            1           32m

NAME                                                   DESIRED   CURRENT   READY   AGE
replicaset.apps/envoy-default-eg-e41e7b31-686d67777f   1         1         1       27m
replicaset.apps/envoy-gateway-5d5757c69                1         1         1       32m



## Contour ##
kubectl -n projectcontour get all
NAME                                READY   STATUS      RESTARTS   AGE
pod/contour-7b494b7646-jdchv        1/1     Running     0          7m52s
pod/contour-7b494b7646-t6ls4        1/1     Running     0          7m53s
pod/contour-certgen-v1-28-2-r4d4m   0/1     Completed   0          7m53s
pod/envoy-czccv                     2/2     Running     0          7m52s

NAME              TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
service/contour   ClusterIP      10.96.3.234     <none>        8001/TCP                     7m53s
service/envoy     LoadBalancer   10.96.158.165   172.17.0.0    80:31998/TCP,443:30734/TCP   7m53s

NAME                   DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/envoy   1         1         1       1            1           <none>          7m53s

NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/contour   2/2     2            2           7m53s

NAME                                 DESIRED   CURRENT   READY   AGE
replicaset.apps/contour-7b494b7646   2         2         2       7m53s

NAME                                COMPLETIONS   DURATION   AGE
job.batch/contour-certgen-v1-28-2   1/1           13s        7m53s

[zirain]

envoy-gateway is the controller, you want to expose it via a LoadBalancer?

[Babbili]

nope, but i'm asking if you have the option of having a service type LoadBalancer, just like project Contour has both options

[zirain]

is this what you're looking for?

[Babbili]

yea thank you, i see that i have envoy-default service type LoadBalancer after applying GatewayClass and Gateway,

NAME                                             READY   STATUS    RESTARTS   AGE
pod/envoy-default-eg-e41e7b31-686d67777f-fjplv   2/2     Running   0          27m
pod/envoy-gateway-5d5757c69-rpbt6                1/1     Running   0          32m

NAME                                TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                         AGE
service/envoy-default-eg-e41e7b31   LoadBalancer   10.96.96.128    172.17.0.0    80:32313/TCP                    27m
service/envoy-gateway               ClusterIP      10.96.217.172   <none>        18000/TCP,18001/TCP,19001/TCP   32m

NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/envoy-default-eg-e41e7b31   1/1     1            1           27m
deployment.apps/envoy-gateway               1/1     1            1           32m

seems like it's applied for HttpRoute and i wonder if i can use Ingress

[zirain]

Envoy Gateway is an open source project for managing [Envoy Proxy](https://www.envoyproxy.io/) as a standalone or Kubernetes-based application gateway. [Gateway API](https://gateway-api.sigs.k8s.io/) resources are used to dynamically provision and configure the managed Envoy Proxies.