Sig-release: Auditing Release Managers who are responsible for upholding the security embargo

[justaugustus]

We have a few contributors within the Release Managers group, who must agree to uphold the Kubernetes security embargo due to the sensitive communications they receive.

While some of this is assumed, I want to capture this in an issue for future auditability.

Already agreed

Patch Release Team

• Aleksandra Malinowska (@aleksandra-malinowska)
• Hannes Hörl (@hoegaarden)
• Pengfei Ni (@feiskyer)
• Tim Pepper (@tpepper)

SIG Chairs

• Caleb Miles (@calebamiles)
• Stephen Augustus (@justaugustus)
• Tim Pepper (@tpepper)

(ref: https://groups.google.com/d/msg/kubernetes-security-discuss/EYpUoONgLUA/DNAc2aa2EwAJ)

Pending

Build Admins

• [x] ~Aleksandra Malinowska (@aleksandra-malinowska) (already agreed; Patch Release Team member)~
• [x] ~Linus Arver (@listx)~
• [ ] ~Sumitran Raghunathan (@sumitranr)~
• [ ] ~Premdeep Sharma (@ps882)~
• [ ] ~Simon Yang (@simony-gke)~
• [x] Aaron Crickenberger @spiffxp
• [x] Amit Watve @amwat
• [x] Benjamin Elder @BenTheElder
• [x] Grant McCloskey @MushuEE

Future Patch Release Team members

• [x] Doug MacEachern (@dougm)
• [x] Yang Li (@idealhack)

(ref: https://github.com/kubernetes/sig-release/issues/737)

I want to file and close this before completing the mailing list membership changes mentioned in https://github.com/kubernetes/sig-release/issues/732.

If you are assigned to this issue, please respond to this issue stating that you agree to abide by the guidelines set forth in the Security Release Process.

If you're not assigned, I'm only tagging you for visibility.

/assign @listx @sumitranr @dougm @idealhack
cc: @kubernetes/release-engineering @kubernetes/product-security-committee @kubernetes/sig-release-admins
/kind documentation
/area release-eng
/sig release
/milestone v1.16
/priority important-soon

[idealhack]

I agree to uphold the Kubernetes security embargo.

[dougm]

I agree to uphold the Kubernetes security embargo.

[listx]

I agree to uphold the Kubernetes security embargo.

[idealhack]

btw, it seems we need to extend the list since we now have a new Build Admin, @ps882, welcome!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[justaugustus]

/remove-lifecycle stale
/milestone v1.18

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[justaugustus]

/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[justaugustus]

New @kubernetes/build-admins -- please respond to this issue stating that you agree to abide by the guidelines set forth in the Security Release Process.

/assign @spiffxp @BenTheElder @amwat @MushuEE

[MushuEE]

I agree to uphold the Kubernetes security embargo.

[spiffxp]

I agree to uphold the Kubernetes security embargo.

[amwat]

I agree to uphold the Kubernetes security embargo.

[BenTheElder]

I agree to uphold the Kubernetes security embargo.

On Thu, Aug 6, 2020 at 11:55 AM Amit Watve [e-mail] wrote:

I agree to uphold the Kubernetes security embargo.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/sig-release/issues/746#issuecomment-670134158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHADK4UAOV5XKSPRJCYG5TR7L4BTANCNFSM4IJQDDVQ
.

[justaugustus]

Good to go!
/close

[k8s-ci-robot]

@justaugustus: Closing this issue.

In response to this:

Good to go!
/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.