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.

Sign up for GitHub

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

Jump to bottom

[Feature] Remove the dependency on modifying k8s apiserver #62

Closed
weilaaa opened this issue Oct 19, 2021 · 1 comment · Fixed by #67
Closed

[Feature] Remove the dependency on modifying k8s apiserver #62

weilaaa opened this issue Oct 19, 2021 · 1 comment · Fixed by #67
Assignees
@zhujf1989 @weilaaa

Comments

@weilaaa
Copy link
Member

weilaaa commented Oct 19, 2021 •
edited
Loading

Why we should remove the dependency on modifying k8s apiserver?

At present, we have to modify the args of k8s apiserver so that auth token can be verified by our auth webhook, but against deployment.

Assumed that there are lots of k8s master nodes, we have to modify each master node one by one. This is unbearable.

A proposal may make sense

Integrate auth proxy in warden.

Warden would parse token for user and do Impersonation with request forwards to k8s apiserver.
@weilaaa weilaaa mentioned this issue Nov 15, 2021
Merged
@weilaaa
Copy link
Member Author

weilaaa commented Jan 19, 2022

already done

@weilaaa weilaaa closed this as completed Jan 19, 2022
@weilaaa weilaaa linked a pull request Jan 19, 2022 that will close this issue
Feature/auth proxy #67
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zhujf1989 zhujf1989

@weilaaa weilaaa

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feature/auth proxy kubecube-io/KubeCube
2 participants
@zhujf1989 @weilaaa