Skip to content
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

Use userinfo.email scope with kube API Client #83

Merged
merged 1 commit into from
Mar 28, 2018

Conversation

jlewi
Copy link
Contributor

@jlewi jlewi commented Mar 27, 2018

  • See userinfo.email scope is needed to work with rbac kubernetes-client/python-base#54
  • We need to provide userinfo.email scope to service accounts when with the K8s python client library.
    • K8s server needs to know the email of the service account because RBAC role bindings can be expressed in terms of the email but without the userinfo.email scope it will end up using the numeric id
      and we will get RBAC roles because of missing bindings.
  • Update the debug worker to use the image in kubeflow-ci.

@jlewi jlewi changed the title Update the debug worker to use the image in kubeflow-ci. Use userinfo.email scope with kube API Client Mar 28, 2018
See:
kubernetes-client/python-base#54
kubernetes-client/python-base#54

* The python client libs need to include userinfo.email when requesting scopes because otherwise RBAC might not work correctly because we won't be able to map the account/user correctly to role/cluster bindings for the email.

* ksonnet doesn't have the fixes to the go client lib so for now we just
update our docs to work around it by including a cluster role binding
for the numeric id.

* Update the debug worker to use the image in kubeflow-ci.
@jlewi
Copy link
Contributor Author

jlewi commented Mar 28, 2018

/assign @lluunn

@lluunn
Copy link
Contributor

lluunn commented Mar 28, 2018

/lgtm

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lluunn

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants