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

kubespray - update list of authorized users #209

Open
vielmetti opened this issue Apr 28, 2022 · 6 comments
Open

kubespray - update list of authorized users #209

vielmetti opened this issue Apr 28, 2022 · 6 comments
Milestone

Comments

@vielmetti
Copy link
Collaborator

In #77 recently we had to scramble a bit to find the right people with Equinix CNCF CIL accounts to have access to the cluster.

For Kubespray it would be good to review the current list, identify any changes, and carry those out.

Attn kubespray: @Miouge1 @mattymo
Attn CNCF: @caniszczyk @jeefy @hh
cc @idvoretskyi

@vielmetti vielmetti added this to the Kubespray milestone Apr 28, 2022
@vielmetti
Copy link
Collaborator Author

In particular it was reported that @riverzhang is not currently active on the project, but has system access, which might be something to correct in some way.

@vielmetti
Copy link
Collaborator Author

has anyone heard from @riverzhang ? I have not.

@hh
Copy link

hh commented May 10, 2022

Last commit was kubernetes-sigs/kubespray@d4a36aa which is Feb 19, 2019. I'm checking in with a couple community members since he hasn't had any Kubespray interactions since 2020.

Note the move to EMERITUS : kubernetes-sigs/kubespray@aeaa876

My suggestion is to ensure that OWNERS:approvers is current, and to remove anyone who isn't in approvers from the infra.

@riverzhang
Copy link

@vielmetti @hh I'm on vacation during this time and I'm sorry I missed these messages.

@jeefy
Copy link
Member

jeefy commented Jun 28, 2022

I feel like this should be handled by the Kubespray folks and not the CNCF. There's not an easy 1:1 mapping of an OWNERS file to emails in an Equinix project. I'd suggest as part of a project's annual report process, they do some housekeeping of resources like this.

Thoughts?

@idvoretskyi
Copy link
Member

@vielmetti I'm curious if any further steps are required here.

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

No branches or pull requests

5 participants