Closed
Description
GitHub Username
Organization you are requesting membership in
kubernetes, 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
Sponsor 2
List of contributions to the Kubernetes project
Involved with CAPZ SIGS project. Authored the following PRs:
- Add disk encryption options documentation kubernetes-sigs/cluster-api-provider-azure#4415
- Add omitempty to SSHPublicKey kubernetes-sigs/cluster-api-provider-azure#5092
- Move webhook registration behind feature gate flag kubernetes-sigs/cluster-api-provider-azure#5099
- Validate identity type on user-assigned identities kubernetes-sigs/cluster-api-provider-azure#5102
- Set default values in API rather than in webhooks kubernetes-sigs/cluster-api-provider-azure#5111
- Add the ability to auth via certs without storing them in etcd secret kubernetes-sigs/cluster-api-provider-azure#5200
- Add a file watcher for Azure client cert auth kubernetes-sigs/cluster-api-provider-azure#5254