Missing resource results in huge error log volume "not found"

[joran-fonjallaz]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When a resource is missing in the cluster, like

• a Service on which an HTTPRoute points
• a Secret on which a Consumer depends
• a Plugin on which an HTTPRoute depends

the KIC controller container creates ~20 log entries per second for each missing dependency. Example here

during POC and discovery phases, it creates absolute madness of logs if things are not cleaned up immediately. I think 1 log entry per second telling that a resource is missing is more than enough.

Expected Behavior

The KIC logs get at max 1 log per second if a resource is missing. Maybe even just a few logs per minute.

Steps To Reproduce

e.g. create an HTTPRoute referring a Service that doesn't exist


apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: echo
  annotations:
    konghq.com/strip-path: 'true'
spec:
  parentRefs:
  - name: kong
  rules:
  - matches:
    - path:
        type: PathPrefix
        value: /echo
    backendRefs:
    - name: nonExistingServiceName # <-- KIC should start logging ~20 logs/second
      kind: Service
      port: 1027

Kong Ingress Controller version

3.3.1

Kubernetes version

1.30.3-gke

Anything else?

Thank you :)

[randmonkey]

@joran-fonjallaz Thanks for pointing out. We will try to optimize logs to reduce excessive amount of error logs.