Release Team Lead access for @leonardpahlke @gracenng @Priyankasaggu11929 @nate-double-u @katcosgrove

[leonardpahlke]

trafficstars

GitHub Username(s)

• @leonardpahlke
• @gracenng
• @nate-double-u
• @katcosgrove
• @Priyankasaggu11929

Release Cycle

Kubernetes 1.26

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

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)
  • milestone-maintainers
  • release-team
  • release-team-leads
  • sig-release
• [x] Update kubernetes/sig-release OWNERS
  • Release Team Lead and Shadows
    • Add an approvers entry in releases/release-x.y/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)
  • k8s-infra-release-viewers@
  • release-managers@
  • release-team@
• [x] Grant calendar access
• [x] Grant Zoom credentials (host key)
• [x] Add incoming leads to release-team-leads Slack Group (kubernetes/community)
  • Add slack ID(s) to users.yaml, if they are not yet in the file
  • Add username(s) to usergroups.yaml

Offboarding

• [ ] Remove from GitHub teams (kubernetes/org)
  • milestone-maintainers
  • release-team
  • release-team-leads
• [ ] Remove from Google Groups/GCP IAM membership (kubernetes/k8s.io)
  • k8s-infra-release-viewers@
  • release-managers@
• [ ] Manually remove from the following Google Groups:
  • kubernetes-release-team (Add as Manager)
  • kubernetes-sig-leads (Add as Member)
• [ ] 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

[leonardpahlke]

I have completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LFzx82j64sv1 I agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[leonardpahlke]

Onboarding of RT leads is completed :)

[palnabarun]

Please make sure that all lead shadows also complete the CNCF Inclusive Speaker Orientation training.

[leonardpahlke]

@Priyankasaggu11929 @nate-double-u @katcosgrove @gracenng, could you comment on your certificate ID number here?

[gracenng]

I have completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LF-ocllb99cdq

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

[Priyankasaggu11929]

I have completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LF-vm42e2205f

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

[katcosgrove]

I have completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LF-ufmbi6ztnx

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

[nate-double-u]

Sorry for the delay, I'm having some login issues with my LF training portal account. I've opened a support ticket and hope to have it resolved soon.

[nate-double-u]

I have completed the CNCF Inclusive Speaker Orientation training. Certificate ID Number: LF-pj1lrok35a

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

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.