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
Is there an existing issue for this?
Current Behavior
When a resource is missing in the cluster, like
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
Kong Ingress Controller version
Kubernetes version
Anything else?
Thank you :)