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
When I create multiple conflicting resources concurrently, for example two Secrets used as JWT credentials with the same key and attached to two KongConsumers, the webhook could not detect the conflict because it is using a cached client for listing resources, so the conflicting KongConsumer and Secret may not be listed in the client if the interval of creating them too quickly.
Then the resources will be translated to invalid Kong configuration and rejected by Kong gateways:
{"message": "declarative config is invalid: {jwt_secrets={\"uniqueness violation: 'jwt_secrets' entity with key set to 'abc123' already declared\"}}"}
This may also happen for other resources with unique restraints on some fields, like username of consumers or prefix of vaults.
Expected Behavior
No invalid Kong configuration generated in such scenario.
The creation of conflicting resource is rejected, or detect the conflicts in translation phase then remove them in translated Kong configuration and generate TranslationError events.
Is there an existing issue for this?
Current Behavior
From FTI-6318.
When I create multiple conflicting resources concurrently, for example two
Secret
s used as JWT credentials with the samekey
and attached to twoKongConsumer
s, the webhook could not detect the conflict because it is using a cached client for listing resources, so the conflictingKongConsumer
andSecret
may not be listed in the client if the interval of creating them too quickly.Then the resources will be translated to invalid Kong configuration and rejected by Kong gateways:
This may also happen for other resources with unique restraints on some fields, like
username
of consumers orprefix
of vaults.Expected Behavior
No invalid Kong configuration generated in such scenario.
The creation of conflicting resource is rejected, or detect the conflicts in translation phase then remove them in translated Kong configuration and generate
TranslationError
events.Steps To Reproduce
Kong Ingress Controller version
Kubernetes version
Anything else?
No response
The text was updated successfully, but these errors were encountered: