-
Notifications
You must be signed in to change notification settings - Fork 591
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
JWT plugin failing to fetch existing secret #4672
Comments
Hello, thanks for the report @CristianPupazan. In |
Hi Jakub,
Any idea what else it could be I am missing? |
Hello Cristian, |
Hi Jakub, Install ingress controller:
where values.yaml:
End to end config:
where kong-configuration.yaml:
Annotate the service
Add credentials to the consumer
Check logs:
|
Also might be worth mentioning that I had to set |
Are your CRDs up to date? We had a similar report internally that cleared after getting the latest CRDs, though it's unclear why (we don't know of a reason why CRD changes would prevent the controller from finding a Secret). the What do you get for this before upgrading?
That may let us roughly pinpoint which version of the CRDs you have to try and understand how it's breaking better. |
It was the CRDs version indeed. I was running on some old version. I just assumed these got updated when we upgraded the ingress via helm. Before:
I run the following to upgrade the CRDs:
Current version:
I've tested and the JWT gets validated now. Thank you all for your help! |
Hi, I got this error again. The CRDs version is v0.13.0 on my side. |
Is there an existing issue for this?
Current Behavior
I am trying to configure the JWT plugin following the instructions here.
I am having trouble provisioning the JWT credentials.
I have tried creating the secret in various ways, all with the same outcome:
kubectl create secret --from-literal
as per the instructionssecret.yaml
as described here.I see the following errors:
Log from the ingress controller:
The proxy gives the following error when providing the jwt token:
Note that the secret is there:
The consumer looks like this:
Expected Behavior
KONG should be able to fetch the secret and validate the JWT token.
Steps To Reproduce
Kubernetes version
The text was updated successfully, but these errors were encountered: