Sig-release: Release Team Lead access for @palnabarun @kikisdeliveryservice @savitharaghunathan @bai

[palnabarun]

GitHub Username(s)

• @palnabarun
• @kikisdeliveryservice
• @savitharaghunathan
• @bai

Release Cycle

Kubernetes 1.21

Prerequisites

• [x] Ensure new Release Team Lead:
  
  
  
  • [x] Has joined the following mailing lists:
  
  
  • kubernetes-sig-release
  
  
  • kubernetes-dev
  
  
  • [x] Has joined the following Slack channels:
  
  
  • #sig-release
  
  
  • #release-management
  
  
  • [x] Is a Kubernetes GitHub org member
  
  
  • [x] Has completed the CNCF Inclusive Speaker Orientation. Please drop in the certification ID in the comments once completed.
  
  
  • [x] Nabarun Pal
  
  
  • [x] Kirsten Garrison
  
  
  • [x] Savitha Raghunathan
  
  
  • [x] Vlad Gorodetsky
  
  

Onboarding

• [x] Release Team Lead has agreed to abide by the guidelines set forth in the
  Security Release Process, specifically the embargo on CVE communications.
  This must be done as an issue comment by the incoming Release Team Lead.
• [x] Update GitHub teams (kubernetes/org) ~> (https://github.com/kubernetes/org/pull/2405)
  
  
  
  • milestone-maintainers
  
  
  • release-team
  
  
  • release-team-leads
  
  
  • sig-release
  
  
• [x] Update kubernetes/sig-release OWNERS ~> (https://github.com/kubernetes/sig-release/pull/1407 and https://github.com/kubernetes/sig-release/pull/1405)
  
  
  
  • Release Team Lead and Shadows
  
  
  • Add an approvers entry in releases/release-1.21/OWNERS
  
  
  • Release Team Lead only
  
  
  • In OWNERS_ALIASES, add an entry in the following sections:
    
    
    
    
    
    • release-team
    
    
    
    • release-team-lead-role
    
    
    
  
  
• [x] Update Google Groups/GCP IAM membership (kubernetes/k8s.io) ~> (https://github.com/kubernetes/k8s.io/pull/1513)
  
  
  
  • k8s-infra-release-viewers@
  
  
  • release-managers@
  
  
• [x] Manually grant access to the following Google Groups:
  
  
  
  • kubernetes-release-team (Add as Manager)
  
  
  • kubernetes-sig-leads (Add as Member)
  
  
• [x] Grant calendar access
• [x] Grant Zoom credentials (host key)
• [x] Add incoming leads to release-team-leads Slack Group (kubernetes/community) ~> (https://github.com/kubernetes/community/pull/5393)
  
  
  
  • Add slack ID(s) to users.yaml, if they are not yet in the file
  
  
  • Add username(s) to usergroups.yaml
  
  

Offboarding

• [x] Remove from GitHub teams (kubernetes/org)
  
  
  
  • milestone-maintainers
  
  
  • release-team
  
  
  • release-team-leads
  
  
• [x] Remove from Google Groups/GCP IAM membership (kubernetes/k8s.io)
  
  
  
  • k8s-infra-release-viewers@
  
  
  • release-managers@
  
  
• [x] Manually remove from the following Google Groups:
  
  
  
  • kubernetes-release-team (Add as Manager)
  
  
  • kubernetes-sig-leads (Add as Member)
  
  
• [x] Remove from release-team-leads Slack Group (kubernetes/community)
  
  
  
  • Remove slack ID(s) from users.yaml, if no longer in a group
  
  
  • Remove username(s) from usergroups.yaml
  
  

cc: @kubernetes/release-engineering @kubernetes/release-team

[palnabarun]

/milestone 1.21

[k8s-ci-robot]

@palnabarun: The provided milestone is not valid for this repository. Milestones in this repository: [next, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22]

Use /milestone clear to clear the milestone.

In response to this:

/milestone 1.21

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.

[palnabarun]

/milestone v1.21

[palnabarun]

I have completed the training. My LF training certificate ID is LF-o61x5t3r6e.

[savitharaghunathan]

I have completed the CNCF Inclusive Speaker Orientation training! Here's my certificate id: LF-a7hzkmrc4m

[savitharaghunathan]

✨ I solemnly swear to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications

[palnabarun]

I solemnly swear to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[bai]

I have completed the training. My training certificate ID is LF-yqwnil3c9f.

I solemnly swear to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[kikisdeliveryservice]

I completed my training: LF-tst9jc3b5s

I solemnly swear to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[palnabarun]

/kind documentation
/kind cleanup
/priority important-soon

[justaugustus]

/assign @justaugustus
/unassign @palnabarun

I'll take care of offboarding as part of some periodic access updates.
Thanks for all of your hard work this cycle team!

[kikisdeliveryservice]

I believe this was done, anything else that we need to do @justaugustus before closing??

[palnabarun]

I have verified the offboarding tasks and checked for the absence of access to the privileged mailing lists. Hence closing this.

Please feel free to reopen this, if it is otherwise.

/assign
/close

[k8s-ci-robot]

@palnabarun: Closing this issue.

In response to this:

I have verified the offboarding tasks and checked for the absence of access to the privileged mailing lists. Hence closing this.

Please feel free to reopen this, if it is otherwise.

/assign
/close

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.