-
Notifications
You must be signed in to change notification settings - Fork 87
Authorization failure on sample operator example, maybe related to OIDC auth #349
Comments
Thank you for reporting it with all the details, especially with the packages. Can you please additionally Kopf contains only a minimal authentication logic of using
More information: I see that |
well, the i'll try to install kubernetes native client and will report later |
@nolar your suggestion worked, |
Hm. That's interesting. What I see in the logs, is that pykube's credentials were retreived and didn't work:
It is unexpected that pykube-ng works interactively. Maybe, the token extraction during auth-piggy-backing is somehow incomplete (but it should as simple as SSL certs & HTTP auth headers extraction, no magic). When you tried it in the console, was it after the My hypothesis is: As far as I remember the internals of |
|
Client auth seems to work ok but operator has issues accessing the api, if I had to guess, I would check/relax RBAC restrictions on what the Operator can do. Play around with Roles, RoleBinding and ClusterRole, ClusterRoleBindings. In OIDC they can bind to different attributes, anything from the token really, custom groups etc. Check under 'watcher' and make sure Operator has RBAC permission to do what you want to do. |
@styk-tv as soon I change k8s client as described abov, all is working. |
Long story short
Trying to run sample operator from the docs, unable to run it. We're using OIDC for k8s cluster authorization.
Description
Using example from https://github.com/zalando-incubator/kopf/tree/master/examples/01-minimal
The exact command to reproduce the issue
The full output of the command that failed
Environment
Python packages installed
The text was updated successfully, but these errors were encountered: