Deployment Option's replicas field

[yasirub]

can we get more info about this issue mentioned in the kong-operator docs?

[pmalek]

Hi @yasirub 👋

This basically says what's visible in the description. You can use this field simply by setting it in spec.deployment like so:

apiVersion: gateway-operator.konghq.com/v1beta1
kind: DataPlane
metadata:
  name: dataplane-example
spec:
  deployment:
    replicas: 3
    podTemplateSpec:
      spec:
        containers:
        - name: proxy
          image: kong:3.4
          env:
          - name: KONG_LOG_LEVEL
            value: debug
          readinessProbe:
            initialDelaySeconds: 1
            periodSeconds: 1

The issue captures a feature which is to implement this for ControlPlanes and for managed Gateways.

Hope that helps.

[yasirub]

Hi, @pmalek
I am trying Kong-operator in my k8s cluster. when I scale up data plane pods to more than 1, only one data plane pod gets configuration updates from control plane.

also control plane pod env CONTROLLER_KONG_ADMIN_URL is specifying up to ip address. In helm chart deployed versions this only specifying service name. is this could be the problem ?

do you have any idea about this issue?

[pmalek]

when I scale up data plane pods to more than 1, only one data plane pod gets configuration updates from control plane.

That's exactly what the mentioned issue is about 🙃 We do have some plans to make more of those visible to end users.

For the time being you can track either https://github.com/Kong/gateway-operator-docs/blob/main/CHANGELOG.md or https://docs.konghq.com/gateway-operator/changelog/ for changes that we include in released versions.

[yasirub]

@pmalek for the time beign I was able to fix this by adding CONTROLLER_KONG_ADMIN_SVC and CONTROLLER_KONG_ADMIN_SVC_PORT_NAMES env variables. But since admin api svc name contains dynamic non predictable part it's not ideal to set it manually.

do you have any get around for this issue?

[pmalek]

I can see you're using the Gateway resource which is in tech preview for now: https://docs.konghq.com/gateway-operator/latest/get-started/kic/create-gateway/.

The particular issue that you're having is lack of support for horizontal DataPlane scaling in managed Gateways which we have on our roadmap.

To workaround this issue you could use separate ControlPlane and DataPlane resources and specify the CONTROLLER_KONG_ADMIN_SVC env variable then (after DataPlane admin service gets created and you know it's name). It's similar approach to what you're already doing but with independently controlled 2 custom resources.

We internally track the support for Gateway Discovery and usage of multiple DataPlanes with Gateway in Kong/kong-operator#607.

Hope that helps!