REQUEST: New membership for hchenxa

[hchenxa]

GitHub Username

@hchenxa

Organization you are requesting membership in

@kubernetes-sigs
@kubernetes

Requirements

• I have reviewed the community membership guidelines (https://git.k8s.io/community/community-membership.md)
• I have enabled 2FA on my GitHub account (https://github.com/settings/security)
• I have subscribed to the kubernetes-dev e-mail list (https://groups.google.com/forum/#!forum/kubernetes-dev)
• 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

Sponsors

• @gyliu513
• @k82cn

List of contributions to the Kubernetes project

• PRs reviewed / authored
  kubernetes:
  only use system namespace when default backend not defined kubernetes#72142
  fix minor typo kubernetes#51072
  disable the logtostderr to write the rescheduler log in file kubernetes#50822

kubernetes/ingress-nginx:
kubernetes/ingress-nginx#3271
kubernetes/ingress-nginx#3252
kubernetes/ingress-nginx#3215
kubernetes/ingress-nginx#3201
kubernetes/ingress-nginx#3111
kubernetes/ingress-nginx#3108
kubernetes/ingress-nginx#3103
kubernetes/ingress-nginx#3100
kubernetes/ingress-nginx#3073
kubernetes/ingress-nginx#3081

cluster-api-provider-openstack:
kubernetes-sigs/cluster-api-provider-openstack#329
kubernetes-sigs/cluster-api-provider-openstack#326
kubernetes-sigs/cluster-api-provider-openstack#314
kubernetes-sigs/cluster-api-provider-openstack#306
kubernetes-sigs/cluster-api-provider-openstack#305
kubernetes-sigs/cluster-api-provider-openstack#224

• Issues responded to
  kubernetes:
  the endpoint can not shown when describe the ingress resource kubernetes#72144
  multiple header shown when get service list  kubernetes#69555
  watch the kubectl changes will be exit after a while kubernetes#67491
  kubectl delete pods hang kubernetes#67479
  apiserver crashed when priority classs already exists kubernetes#67367
  The pod still be secheduled on NotReady pods after evicted kubernetes#67300
  fatal error throws when enable the --clean-up flags for kube proxy kubernetes#66819
  command panic when use kubectl to get the pods list kubernetes#66597
  [Question]Does nodeLabelRole support multiple values? kubernetes#65738
  the status of volumeClaimTemplates was pending even if the pvc was created already kubernetes#65706
  kubelet can not connect to apiserver when the number of nodes increase to 1500 kubernetes#64014
  All pod was running but the number was available was not updated for daemonset kubernetes#63052
  Unable to release resource in resource-quota when scale down deployment kubernetes#62828
  [Question]Does kubelet can GC the dead docker containers? kubernetes#62907
  apiserver panic when call endpoints API. kubernetes#56278
  [Question]How to get the command return code in kubernetes kubernetes#55211
  can not get pod image name by jsonpath when use label selector kubernetes#54851
  kubeproxy started failed due to null point exceptions kubernetes#51680
  Controller manager NPE because some controllers aren't ready to receive shared informer events immediately after adding handlers kubernetes#51013
  controller manager existed in HA topology due to list watch timeout kubernetes#51002
  The rescheduler can not be started up due to the stdout point to a directory kubernetes#50820

kubernetes/ingress-nginx:
kubernetes/ingress-nginx#3273
kubernetes/ingress-nginx#3272
kubernetes/ingress-nginx#3268
kubernetes/ingress-nginx#3071
kubernetes/ingress-nginx#3031

cluster-api-provider-openstack:
kubernetes-sigs/cluster-api-provider-openstack#325
kubernetes-sigs/cluster-api-provider-openstack#318
kubernetes-sigs/cluster-api-provider-openstack#315
kubernetes-sigs/cluster-api-provider-openstack#307
kubernetes-sigs/cluster-api-provider-openstack#304
kubernetes-sigs/cluster-api-provider-openstack#301

• SIG projects I am involved with
  cluster-api-provider-openstack

[gyliu513]

+1, thanks @hchenxa for your great contribution!

[xunpan]

+1, looking forward more active contributions to sig-kubernetes projects.

[k82cn]

+1 to me, thanks for your contribution :)

[mrbobbytables]

Hey there @hchenxa, unfortunately @gyliu513 cannot sponsor you for membership in the @kubernetes org, but CAN sponsor you for membership in @kubernetes-sigs.

An approver/reviewer in @kubernetes, may sponsor someone for the @kubernetes org or any of the related organizations (@kubernetes-sigs, @kubernetes-csi etc); as long as it's a project they're involved with.

However, this does not work the other way around. A sponsor that is only an approver/reviewer in @kubernetes-csi cannot sponsor someone for membership in @kubernetes. They are scoped just to the org they're associated with.

@hchenxa If you'd like to amend your request to just @kubernetes-sigs, we can proceed with getting your membership processed. Otherwise, if you could, please find another sponsor from the @kubernetes org.

If you have any questions don't be afraid to ask.

Thanks!

[wanghaoran1988]

+1 from me, thanks.

[mrbobbytables]

Great :) Thanks for adding your +1 for the kubernetes org @wanghaoran1988.

@hchenxa Thank you for all your contributions thus far 👍

I've created PR #775 to add you to both the kubernetes and kubernetes-sigs orgs. Once that gets merged, you should get a membership invite notification from both of them.

Welcome to @kubernetes! 🎉

/assign