HTTP

Set up an HTTP listener on your API gateway.

notifications

If you followed the Get started guide, you already have a gateway named http in the gloo-system namespace of your cluster. This gateway can be used as the main ingress for the apps in your cluster. HTTPRoutes can refer to this gateway independent of the namespace they are in. To create more gateways, use the instructions in this guide.

Create a gateway resource with an HTTP listener.

  kubectl apply -f- <<EOF
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: my-http-gateway
  namespace: gloo-system
  labels:
    example: httpbin-mydomain
spec:
  gatewayClassName: gloo-gateway
  listeners:
  - protocol: HTTP
    port: 8080
    hostname: mydomain.com
    name: http
    allowedRoutes:
      namespaces:
        from: All
EOF

Setting	Description
`spec.gatewayClassName`	The name of the Kubernetes gateway class that you want to use to configure the gateway. When you set up Gloo Gateway, a default gateway class is set up for you. To view the gateway class configuration, see Gateway classes and types.
`spec.listeners`	Configure the listeners for this gateway. In this example, you configure an HTTP gateway that listens for incoming traffic for the `mydomain.com` domain on port 8080. The gateway can serve HTTP routes from any namespace.

Check the status of the gateway to make sure that your configuration is accepted and no conflicts exist in your cluster.
```
  kubectl get gateway my-http-gateway -n gloo-system -o yaml
  
```

Create an HTTPRoute resource for the httpbin app that is served by the gateway that you created.

  kubectl apply -f- <<EOF
apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  name: httpbin-mydomain
  namespace: httpbin
  labels:
    example: httpbin-mydomain
spec:
  parentRefs:
    - name: my-http-gateway
      namespace: gloo-system
  rules:
    - backendRefs:
        - name: httpbin
          port: 8000
EOF

Verify that the HTTPRoute is applied successfully.

  kubectl get httproute/httpbin-mydomain -n httpbin -o yaml

Get the external address of the gateway and save it in an environment variable.

  export INGRESS_GW_ADDRESS=$(kubectl get svc -n gloo-system gloo-proxy-my-http-gateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
echo $INGRESS_GW_ADDRESS

  export INGRESS_GW_ADDRESS=$(kubectl get svc -n gloo-system gloo-proxy-my-http-gateway -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
echo $INGRESS_GW_ADDRESS

  kubectl port-forward deployment/gloo-proxy-my-http-gateway -n gloo-system 8080:8080

Send a request to the httpbin app and verify that you get back a 200 HTTP response code.

  curl -vik http://$INGRESS_GW_ADDRESS:8080/status/200 -H "host: mydomain.com:8080"

  curl -vik localhost:8080/status/200 -H "host: mydomain.com"

Example output:

  * Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< access-control-allow-credentials: true
access-control-allow-credentials: true
< access-control-allow-origin: *
access-control-allow-origin: *
< date: Fri, 03 Nov 2023 20:02:48 GMT
date: Fri, 03 Nov 2023 20:02:48 GMT
< content-length: 0
content-length: 0
< x-envoy-upstream-service-time: 1
x-envoy-upstream-service-time: 1
< server: envoy
server: envoy

Optional: If you no longer need the HTTP listener, clean up the resources that you created.
```
  kubectl delete -A gateways,httproutes -l example=httpbin-mydomain
  
```