Replies: 3 comments 4 replies
-
Thanks for reporting this issue, but as this is reported against an older and unsupported release we are not able to evaluate the issue. Please verify with the nightly build or the latest release. If the issue can be reproduced in the nightly build or latest release add a comment with additional information, otherwise this issue will be automatically closed within 14 days. |
Beta Was this translation helpful? Give feedback.
-
As the bot comment requests, do you see the same behavior on later Keycloak versions? A 401 would indicate a authorization issue. The RBAC included with the operator gives it permission to watch all the necessary resources. How did you install the operator? |
Beta Was this translation helpful? Give feedback.
-
We’re encountering the same error here. The operator has been working for a long time, and only recently have we started getting this error. Restarting the operator seems to resolve the issue, but it reappears after a while. It appears to be related to the expiration of the JWT token associated with the service account. Although the token is replaced by Kubernetes, it seems that the client is not using the new token. Version: 24.0.4 ( and very recently upgraded Keycloak and it's operator to 25.0.6 but same issue) EDIT: as a workaround to have the operator always available, I used following hacky trick to make it restart every hour:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Before reporting an issue
Area
operator
Describe the bug
Hi Support Team,
We found out an log error where keycloak-operator cannot access secret keycloak-db 401.
Any suggestion to resolve this issue would be very much appreciated!
Thanks!
Environment:
kubectl version
): 1.29Version
24.0.3
Regression
Expected behavior
No error
Actual behavior
As described error
How to Reproduce?
Deploy Keycloak-operator to EKS
Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions