Tao Yi

@balait4 @gcamus59 Could you please try with the latest KIC 3.4? We have fixed an issue related to `KongUpstreamPolicy`: https://github.com/Kong/kubernetes-ingress-controller/pull/6767 in the release. I did not reproduce the issues with...

Closing as "not planned" because it cannot be reproduced and no more context is given for a week.

The specification of the interface between CP and DP is defined here: https://github.com/Kong/openrpc_specfiles/tree/main/kong_sync/v2. The basic architecture of the incremental sync: (0) CP connect to DP by websocket (1) CP notifies...

Closing it as we do not plan to add new features in KIC. Also we are not sure about plans for acting as an incremental config control plane in Kong...

I think the code here may cause client not correctly initialized in Konnect config syncer: https://github.com/Kong/kubernetes-ingress-controller/blob/3dce2d3316716121f015907614728fac899ebdce/internal/manager/run.go#L284 When the konnect client is not created before we setup Konnect config syncer, the...

Can you dump the full status of your load balancer service by `kubectl get service -n `? Kong Ingress Controller (KIC) will choose the first ingress IP of loadbalancer (`status.loadBalancer.ingress.ip[0]`)...

This should be the problem of your k8s provider because it did not update the `status.loadBalancer` of your service. KIC can only read the load balancer IP from the `status.loadBalancer`...