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 realize this is not the best way to put the custom CA file inside the pods, but I just want to accomplish a PoC. I have also tried using a configmap to mount the custom CA certificate file inside the pods and got the same results.
After the pod is running, trying a curl from another pod inside the same cluster, as the docs suggest, gives me the following error:
Adding to this, I've noticed that providing a wrong auth token results in an authentication failure, so this exception is only raised when the token is valid.
I'm wondering if this is a mistake on my end or a bug, and would appreciate any help.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
gustavofaganello
changed the title
[k8s-keystone-auth] Providing a CA certificate raises exception
[k8s-keystone-auth] TokenReview raises exception
Jan 16, 2025
Originally, I thought this was an issue with the --keystone-ca-file option, but I'm still getting the same error when trying a keystone endpoint signed with a public CA. I've adjusted the issue title and description accordingly.
Hello, folks.
I've encountered an issue while trying to request a TokenReview with the k8s-keystone-auth image.
All I've done until now was following these docs.
This is my deployment definition:
And this is my
keystone-auth-certs
secret:I realize this is not the best way to put the custom CA file inside the pods, but I just want to accomplish a PoC. I have also tried using a configmap to mount the custom CA certificate file inside the pods and got the same results.
After the pod is running, trying a curl from another pod inside the same cluster, as the docs suggest, gives me the following error:
For the sake of clarity, this is the curl I'm running and its return:
Adding to this, I've noticed that providing a wrong auth token results in an authentication failure, so this exception is only raised when the token is valid.
I'm wondering if this is a mistake on my end or a bug, and would appreciate any help.
Thanks in advance!
The text was updated successfully, but these errors were encountered: