Improve the Netlify access model

[cahillsf]

Right now only limit people have access to the Netlify and for doing any thing regarding Netlify the people with access have to do some manual work. There is scope to improve this, either through more automation or more shared access.

Carryover from: #9104

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[cahillsf]

@nawazkh @furkatgofurov7 you're listed for this one, want to continue pushing this forward? also would appreciate your feedback on prioritization for the issue board 🙇

[cahillsf]

/area release

[fabriziopandini]

My two cents is to not over-engineering this but just to document the process because ultimately we need to access Netlify only one or two times a year (or even less)

[sbueringer]

Just want to mention that Netlify access is out of our control. I think you'll have to talk to sig-contribex if you want to change something about how all of this works.

[cahillsf]

re the docs, for a start might be helpful to provide some direction for who currently has access (docs seem to just say "someone with access to Netlify" src). @sbueringer @fabriziopandini any ideas for better phrasing here? do all the maintainers have access?

last cycle i believe Cecile helped us with this (#6017 (comment)) but i am aware she is taking a step back from the project

[sbueringer]

I have access. IIRC @fabriziopandini as well. Very likely @vincepri as well.

[nawazkh]

@furkatgofurov7 and I were looking into this issue earlier, and the TL;DR is that "Today there is no automation for Netlify access, however there's a handful of people to handle access / requests for "all sites" (spanning SIGs / companies / contributors - to handle redundancy). It would be awesome to build something to automate it."

Reference conversation: https://kubernetes.slack.com/archives/C8TSNPY4T/p1697826615480259?thread_ts=1697826166.088039&cid=C8TSNPY4T

[fabriziopandini]

+1 to improve the doc with the list of people having access (or just maintainers, the list ~overlaps) for now.
/kind documentation
/triage accepted

[sbueringer]

I think neither Killian nor Christian have Netlify access. I suspect Alberto also doesn't have it.

[fabriziopandini]

Just checked
There is Cecile, Vince, Me, Stefan, Jack, Matt (Invite Pending)
We can add more by asking to ContribEx

[cahillsf]

just opened a small PR, lmk if this is sufficient