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

kubecfg handler renders config with hardcoded user #45

Open
UiP9AV6Y opened this issue Jan 26, 2022 · 0 comments · May be fixed by #48
Open

kubecfg handler renders config with hardcoded user #45

UiP9AV6Y opened this issue Jan 26, 2022 · 0 comments · May be fixed by #48

Comments

@UiP9AV6Y
Copy link

the kubecfg endpoint renders the kubectl configuration file with a token generated for the authenticated user, but uses a hardcoded user for the user and context sections.

the resulting output can not be used as-is and requires post-processing on the consumer side.
UiP9AV6Y added a commit to UiP9AV6Y/kubehook that referenced this issue Jan 26, 2022
@UiP9AV6Y
render kube config using the authenticated user.
6dda52b 
instead of a hardcoded value, the configuration file uses the user
information from the authentication context for the user and context
settings.

closes planetlabs#45
@UiP9AV6Y UiP9AV6Y linked a pull request Jan 26, 2022 that will close this issue
Open
UiP9AV6Y added a commit to UiP9AV6Y/kubehook that referenced this issue Jan 31, 2022
@UiP9AV6Y
render kube config using the authenticated user.
8ce9c97 
instead of a hardcoded value, the configuration file uses the user
information from the authentication context for the user and context
settings.

closes planetlabs#45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

render kube config using the authenticated user. UiP9AV6Y/kubehook
1 participant
@UiP9AV6Y