KongConfigurationTranslationFailed: failed fetching KongUpstreamPolicy: KongUpstreamPolicy

[nikhil-anand-zn]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I have added KongUpstreamPolicy in my EKS cluster. Facing KongUpstreamPolicy not found error, upon annotating the service.

2025-07-30 17:08:45.670 | 2025-07-30T11:38:45Z	error	recording a Warning event for object	{"name": "example", "namespace": "example", "kind": "Service", "apiVersion": "/v1", "reason": "KongConfigurationTranslationFailed", "message": "failed fetching KongUpstreamPolicy: KongUpstreamPolicy example/example-health-checking not found", "error": "object failed to apply"} |  
2025-07-30 17:08:45.664 | 2025-07-30T11:38:45Z	error	failed fetching KongUpstreamPolicy: KongUpstreamPolicy example/example-health-checking not found	{"name": "example", "namespace": "example", "GVK": "/v1, Kind=Service", "error": "resource processing failed"}

Althouhg, controllers.KongUpstreamPolicy started properly, below are logs:

2025-07-30 16:24:07.620 | 2025-07-30T10:54:07Z	info	controllers.KongUpstreamPolicy	Starting EventSource	{"v": 0, "source": "channel source: 0xc0001f5340"} |  
2025-07-30 16:24:07.620 | 2025-07-30T10:54:07Z	info	controllers.KongUpstreamPolicy	Starting EventSource	{"v": 0, "source": "channel source: 0xc0001f5260"} |  
2025-07-30 16:24:07.620 | 2025-07-30T10:54:07Z	info	controllers.KongUpstreamPolicy	Starting EventSource	{"v": 0, "source": "kind source: *v1.HTTPRoute"} |  
2025-07-30 16:24:07.620 | 2025-07-30T10:54:07Z	info	controllers.KongUpstreamPolicy	Starting EventSource	{"v": 0, "source": "kind source: *v1.Ingress"} |  
2025-07-30 16:24:07.620 | 2025-07-30T10:54:07Z	info	controllers.KongUpstreamPolicy	Starting EventSource	{"v": 0, "source": "kind source: *v1.Service"} |  
2025-07-30 16:24:07.620 | 2025-07-30T10:54:07Z	info	controllers.KongUpstreamPolicy	Starting EventSource	{"v": 0, "source": "kind source: *v1beta1.KongUpstreamPolicy"} |  
2025-07-30 16:23:52.732 | 2025-07-30T10:53:52Z	info	controllers.KongUpstreamPolicy	All workers finished	{"v": 0}

Above issue was fixed in #5729, but it KIC has again started throwing this issue.

Expected Behavior

Existing KongUpstreamPolicies should be fetched correctly by the kong ingress-controller

Steps To Reproduce

1. Use kong ingress controller version 3.3
2. Create a KongUpstreamPolicy
3. Annotate the service with konghq.com/upstream-policy: example-health-checking (name of KongUpstreamPolicy)

All objects are in same namespace

Kong Ingress Controller version

3.3

Kubernetes version

1.30

Anything else?

No response