k8s gateway api - setting up gateway and routes to different service in a cluster

 

To setup a k8s gateway api in a gke cluster, you typically have to 

- create gatewayapi

- setup necessary http route 

- deploy your services A and service B.

Setting up gateway by running the following yaml


apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: my-shared-gateway
spec:
  gatewayClassName: gke-l7-regional-external-managed
  listeners:
    - protocol: HTTP # Or HTTPS for production
      port: 80 # Or 443 for HTTPS
      name: http
      hostname: "*.example.com"

create your http route A.

apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: a-route
  namespace: default
spec:
  parentRefs:
  - name: my-shared-gateway
  hostnames:
  - "a.example.com"
  rules:
  - matches:
    - path:
        type: PathPrefix
        value: /
    backendRefs:
    - name: a-service
      port: 80

create http route b

apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: b-route
  namespace: default
spec:
  parentRefs:
  - name: my-shared-gateway
  hostnames:
  - "b.example.com"
  rules:
  - matches:
    - path:
        type: PathPrefix
        value: /
    backendRefs:
    - name: b-service
      port: 80


Next, you can deploy your service A:


apiVersion: apps/v1
kind: Deployment
metadata:
  name: a-deployment
  labels:
    app: a
spec:
  replicas: 1
  selector:
    matchLabels:
      app: a
  template:
    metadata:
      labels:
        app: a
    spec:
      containers:
      - name: hello
        image: hashicorp/http-echo
        args:
        - "-text=Hello from Service A"
        ports:
        - containerPort: 5678
---
apiVersion: v1
kind: Service
metadata:
  name: a-service
spec:
  selector:
    app: a
  ports:
  - protocol: TCP
    port: 80
    targetPort: 5678

Next, you can deploy your service B

apiVersion: apps/v1
kind: Deployment
metadata:
  name: b-deployment
  labels:
    app: b
spec:
  replicas: 1
  selector:
    matchLabels:
      app: b
  template:
    metadata:
      labels:
        app: b
    spec:
      containers:
      - name: hello
        image: hashicorp/http-echo
        args:
        - "-text=Hello from Service B"
        ports:
        - containerPort: 5678
---
apiVersion: v1
kind: Service
metadata:
  name: b-service
spec:
  selector:
    app: b
  ports:
  - protocol: TCP
    port: 80
    targetPort: 5678


The github repo for this setup can be found here.

https://github.com/mitzenjeremywoo/k8s-gateway-api-differnet-host-routing





Comments

Post a Comment

Popular posts from this blog

gemini cli getting file not defined error

Image
 While trying to run gemini cli on my windows linux subsystem, i bump into this error here - "/Roaming/npm/node_modules/@google/gemini-cli/node_modules/undici/lib/web/webidl/index.js:512 webidl.is.File = webidl.util.MakeTypeAssertion(File)"  "ReferenceError: File is not defined" In Node.js, there’s no built-in File (until very recent Node 20+ with experimental WHATWG APIs). So, unless polyfilled, File is undefined, leading to the ReferenceError. And to resolve this, I had to upgrade to node 22 (might work for node 20) and then I was able to run it.
Read more

NodeJS: Error: spawn EINVAL in window for node version 20.20 and 18.20

Encounter this issue when running autorest (that uses nodejs).  I am using node version:  v18.20.2 After i revert to use node v18.12.0, then i was able to get my app to run without this error. Since i am working with Azure devops yaml, i was able to use the following to resolve my issue.  - task : NodeTool@0   inputs :     versionSource : 'spec'     versionSpec : '18.18.0'
Read more

vllm : Failed to infer device type

Trying to run vllm without gpu will typicaly lands you into this issue. To resolve this issue: we can use set these both. Setting one does not work for me. So i had to configure both settings below:- 1.  environment variable CUDA_VISIBLE_DEVICES = "" 2. in the command line, change to use device cpu and remove  tensor-parallel-size. For example, python3 -m vllm.entrypoints.openai.api_server --port 8080 --model deepseek-ai/DeepSeek-R1 --device cpu --trust-remote-code --max-model-len 4096" References https://docs.vllm.ai/en/latest/getting_started/troubleshooting.html#failed-to-infer-device-type
Read more