You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As investigated in Kong/kubernetes-ingress-controller#5389, the FillID() method may generate the same ID for different entities with same "key" in different workspaces. However, ID should be unique through ALL workspaces. This will bring conflicts in configurations.
For example, if two consumers in different workspaces have the same username, we will generate the same ID for the two consumers. Then one of them will receive a "ID already exist" error as described in Kong/kubernetes-ingress-controller#5389. To resolve this, we need to consider workspace of the entity to generate ID from.
The text was updated successfully, but these errors were encountered:
As investigated in Kong/kubernetes-ingress-controller#5389, the FillID() method may generate the same ID for different entities with same "key" in different workspaces. However, ID should be unique through ALL workspaces. This will bring conflicts in configurations.
For example, if two consumers in different workspaces have the same
username
, we will generate the same ID for the two consumers. Then one of them will receive a "ID already exist" error as described in Kong/kubernetes-ingress-controller#5389. To resolve this, we need to consider workspace of the entity to generate ID from.The text was updated successfully, but these errors were encountered: