FillID breaks syncing with duplicate consumers in different namespaces/workspaces #5597
Closed
1 task done
Labels
bug
Something isn't working
pending author feedback
stale
Will be closed unless advocated for within 7 days
Is there an existing issue for this?
Current Behavior
Scenario:
2 KICs watching different namespaces (A+B)
Both pointing to 1 Gateway
Each using a different kong_workspace
2 duplicate KongConsumer objects (1 in namespace A, 1 in namespace B)
With FillID enabled, we see that the KICs are using the exact same UUID for the consumers when pushing them to Kong, causing errors. This is because we are now generating that UUID based on the objects content. In this case the content is exactly the same
KongConsumers:
apiVersion: configuration.konghq.com/v1
kind: KongConsumer
metadata:
name: "apim-consumer"
namespace: sp1
annotations:
kubernetes.io/ingress.class: kong1
username: apim
custom_id: apim
apiVersion: configuration.konghq.com/v1
kind: KongConsumer
metadata:
name: "apim-consumer"
namespace: sp2
annotations:
kubernetes.io/ingress.class: kong2
username: apim
custom_id: apim
Expected Behavior
This flow worked previously and with FillIDs set to off
Kong Gateway allows for this configuration where you have the same consumer defined in multiple workspaces
Steps To Reproduce
No response
Kong Ingress Controller version
Kubernetes version
No response
Anything else?
N/A
The text was updated successfully, but these errors were encountered: