Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GatewAPI gateway address field overriden with publish service #6953

Open
1 task done
hassanbsee2071 opened this issue Jan 13, 2025 · 0 comments
Open
1 task done

GatewAPI gateway address field overriden with publish service #6953

hassanbsee2071 opened this issue Jan 13, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@hassanbsee2071
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I applied below manifest files.

apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
  name: kong-class-multi
  annotations:
    konghq.com/gatewayclass-unmanaged: 'true'

spec:
  controllerName: konghq.com/kic-gateway-controller-multi
---
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: kong-gateway-hotels
  namespace: public-gateway-http
  # annotations:
  #   konghq.com/publish-service: kong-multi/kong-multi-hotels-gateway-proxy
spec:
  gatewayClassName: kong-class-multi
  listeners:
  - name: http-hotels
    port: 80
    protocol: HTTP
    allowedRoutes:
      namespaces:
        from: Selector
        selector:
          matchLabels:
            kubernetes.io/metadata.name: "hotels"
  addresses:
    - type: Hostname
      value: kong-multi-hotel-gateway-86435522.eu-west-1.elb.amazonaws.com

Even though I have specifically mention the addresses in the gateway but it is not reflecting. Load balancer address of publish service is taking over this address.

kubectl get gateway -n public-gateway-http
NAME                        CLASS              ADDRESS                                                                         PROGRAMMED   AGE
kong-gateway-common-teams   kong-class-multi   k8s-kongmult-kongmult-72545a7b88-75418e3312e5914b.elb.eu-west-1.amazonaws.com    True         36h
kong-gateway-flights        kong-class-multi  k8s-kongmult-kongmult-72545a7b88-75418e3312e5914b.elb.eu-west-1.amazonaws.com    True         36h
kong-gateway-hotels         kong-class-multi   k8s-kongmult-kongmult-72545a7b88-75418e3312e5914b.elb.eu-west-1.amazonaws.com   True         54m

I want to create 4 gateways and all 4 gateways have their own load balancers address to listen on. But as you can see above all the gateways have same address. This address is the load balancer of publish service.

Expected Behavior

Each gateway should reflect its own address, instead of same address.

Steps To Reproduce

No response

Kong Ingress Controller version

kubernetes-ingress-controller 3.4

Kubernetes version

Client Version: v1.31.1
Kustomize Version: v5.4.2
Server Version: v1.30.8-eks-2d5f260

Anything else?

No response

@hassanbsee2071 hassanbsee2071 added the bug Something isn't working label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant