Ingress Gateways, API Gateways, Terminating Gateways

Consul
1

I have an mTLS open source install of Consul 1.19.x on kubernetes. We’re using a Sectigo certs for the root CA. I’m having difficulty getting the various gateways to show up. I finally got an API gateway to show up but can’t figure out how to call it. No conceivable URL pattern seems to work. And if I did get it going, is an API gateway specifically geared towards a single Service? It looks as though an API gateway can distribute various URI paths to different services, so maybe you only need one? Any advice welcome. I am a developer, not a Platform Engineering guy, so some of these tools are a little foreign to me.

Thanks!

2

Hi Jason,
Thanks for reaching out! The API gateway can route to multiple services; however, you need to attach an HTTPRoute to the Gateway in order for it to route anywhere. I’m curious if you’ve defined any route(s) yet. If not, the documentation for those is here.

3

Hey, thanks for answering!

I do have an HTTPRoute attached. Here is the definition:

apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  name: mtls-server-route
  namespace: consul
spec:
  parentRefs:
    - name: ingress-gateway
  hostnames:
    - "*"
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: "/"
      backendRefs:
        - name: mtls-server
          namespace: default
          port: 8080 # Target port on the mtls-server service

The question is, how do I calculate an actual URL from this? I’ve tried every combination I can imagine and none answer.

Thanks!