REQUEST: New kubernetes-sigs membership for @pmengelbert

[pmengelbert]

GitHub Username

pmengelbert

Organization you are requesting membership in

kubernetes-sigs

Requirements

• I have reviewed the community membership guidelines
• I have enabled 2FA on my GitHub account
• I have subscribed to the kubernetes dev e-mail list
• I am actively contributing to 1 or more Kubernetes subprojects
• I have two sponsors that meet the sponsor requirements listed in the community membership guidelines
• I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
• I have verified that my sponsors are from different member companies
• I have verified that my sponsors are a reviewer or an approver in at least one OWNERS file within one of the Kubernetes GitHub organizations (excluding the contributor-playground)
• SUGGESTED: Ensure your affiliation in gitdm is up to date (gitdm is used by devstats to track affiliation)
• SUGGESTED: Ensure your affiliation in openprofile.dev is up to date (used by LFX Insights to track affiliation, will replace gitdm in the future)
• SUGGESTED: I have taken the Inclusive Open Source Community Orientation course

Sponsor 1

enj

Sponsor 2

aramase

List of contributions to the Kubernetes project

I am maintaining secrets-store-csi-driver and need kubernetes-sigs membership in order to run tests on PRs to that repo.

• Add client-go credential plugin allowlist to kuberc kubernetes#134870
• Rename name to command in kuberc credentialPluginAllowlist entries kubernetes#137272
• Add credential pluginkubectl kuberc set options kubernetes#137300
• KEP-6060: Implement webhook authentication token issuance and validation kubernetes#140113
• [KEP-3104] Update KEP with credential plugin allowlist enhancements#5479
• KEP-3104 Add kubectl kuberc options for plugin policy/allowlist enhancements#5896
• KEP-6060: API Server Authentication to Webhooks enhancements#6156
• Fix secret update hotloop kubernetes-sigs/secrets-store-csi-driver#2065

[enj]

+1 from me 😄

[jasonbraganza]

@pmengelbert, suggest you change aramase as a sponsor, since enj has already +1ed and because membership guidelines require that sponsors be from different organisations.

Sponsored by 2 reviewers. Note the following requirements for sponsors:
  * Sponsors must have close interactions with the prospective member - e.g. code/design/proposal review, coordinating on issues, etc.
  * Sponsors must be reviewers or approvers in at least one OWNERS file within one of the [Kubernetes GitHub organizations](https://github.com/kubernetes/community/blob/master/github-management#actively-used-github-organizations)
  * Sponsors must be from multiple member companies to demonstrate integration across community.