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
I am facing errors like these (from the kong logs):
2025-02-04T18:26:45Z info admission-server Object admission request not allowed {"v": 0, "name": "auth0-consumer-secret", "kind": "Secret", "namespace": "networking", "message": "consumer credential failed validation: unique key constraint violated for key"}
2025-02-04T18:26:45Z info admission-server Object admission request not allowed {"v": 0, "name": "grafana-key-auth-consumer-secret", "kind": "Secret", "namespace": "grafana", "message": "consumer credential failed validation: unique key constraint violated for key"}
I know the key field of each of these secrets need to be unique, so i decided to use filterSecrets: true config with the label konghq.com/validate: "true" on the secrets to narrow down the conflicting secrets.
If i filter all secrets with that annotation in the whole cluster, i get these too as the unique ones.
k get secrets --all-namespaces -l "konghq.com/validate=true"
NAMESPACE NAME TYPE DATA AGE
grafana grafana-key-auth-consumer-secret Opaque 2 5h44m
networking auth0-consumer-secret Opaque 5 5h52m
But still each time i try to sync on argocd i get the following errors again:
one or more objects failed to apply, reason: error when patching "/dev/shm/2190820843": admission webhook "secrets.credentials.validation.ingress-controller.konghq.com" denied the request: consumer credential failed validation: unique key constraint violated for key,error when patching "/dev/shm/1637693030": admission webhook "secrets.plugins.validation.ingress-controller.konghq.com" denied the request: consumer credential failed validation: unique key constraint violated for key
Any idea what can be the problem here? i am using kong on the dbless mode.
Thank you so much
The text was updated successfully, but these errors were encountered:
While using this config for the kong helm chart:
I am facing errors like these (from the kong logs):
I know the key field of each of these secrets need to be unique, so i decided to use
filterSecrets: true
config with the labelkonghq.com/validate: "true"
on the secrets to narrow down the conflicting secrets.If i filter all secrets with that annotation in the whole cluster, i get these too as the unique ones.
But still each time i try to sync on argocd i get the following errors again:
Any idea what can be the problem here? i am using kong on the dbless mode.
Thank you so much
The text was updated successfully, but these errors were encountered: