Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FillID breaks syncing with duplicate consumers in different namespaces/workspaces #5597

Closed
1 task done
jeffrey-arndt opened this issue Feb 8, 2024 · 3 comments
Closed
1 task done
Labels
bug Something isn't working pending author feedback stale Will be closed unless advocated for within 7 days

Comments

@jeffrey-arndt
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

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

{
	"code": 4,
	"name": "foreign key violation",
	"fields": {
		"@referenced_by": "acls"
	},
	"message": "an existing 'acls' entity references this 'consumers' entity"
}

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

3.0+ (FillID enabled by default)

Kubernetes version

No response

Anything else?

N/A

@jeffrey-arndt jeffrey-arndt added the bug Something isn't working label Feb 8, 2024
@randmonkey
Copy link
Contributor

@jeffrey-arndt We have fixed the duplicate ID problem in KIC 3.1: #5401. Can you upgrade KIC to 3.1 and test it again?
For workaround, you can also add FillID=false in feature gates to turn off FillID if you are not using Konnect integration.

Copy link

stale bot commented Mar 17, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Will be closed unless advocated for within 7 days label Mar 17, 2024
@randmonkey
Copy link
Contributor

Already fixed bug and no further replies from author, close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pending author feedback stale Will be closed unless advocated for within 7 days
Projects
None yet
Development

No branches or pull requests

2 participants