feiskyer
Follow
Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign up
Pinned
1,299 contributions in the last year
Activity overview
Contributed to
kubernetes/kubernetes,
kubernetes-sigs/cloud-provider-azure,
kubernetes/autoscaler
and 5 other
repositories
Contribution activity
August 2020
Created a pull request in kubernetes/kubernetes that received 8 comments
Ensure backoff step is set to 1 for Azure armclient
What type of PR is this? /kind bug What this PR does / why we need it: Ensure backoff step is set to 1 for Azure armclient. When the clients passe…
+20
−3
•
8
comments
- Remove azure-load-balancer-disable-tcp-reset annotation
- fix(azure): check error returned by scaleSet.getVMSS
- Azure Cloud Provider should support Service annotations that allow for ip-tag control over the public ips created for LoadBalancer Services
- Add metrics for azure service operations (route and loadbalancer).
- fix: use sensitiveOptions on Windows mount
- ARM client: survive empty response and error
- Fix deleting loadbalancer after resource group in azure
- fix: azure disk resize error if source does not exist
- Cherry pick of #93107: Azure: use per-vmss vmssvm incremental cache
- Cherry pick of #93107: Azure: use per-vmss vmssvm incremental cache
- Cherry pick of #93107: Azure: use per-vmss vmssvm incremental cache
- Automated cherry pick of #93034: Skip ensuring VMSS in pool for nodes which should be excluded
- Automated cherry pick of #93034: Skip ensuring VMSS in pool for nodes which should be excluded
- Automated cherry pick of #93034: Skip ensuring VMSS in pool for nodes which should be excluded
- Break up the logic in azure_manager
- Cherry pick the bug fix in #2418 onto 1.19
- Cherry pick the bug fix in #2418 onto 1.18
- Cherry-pick onto 1.19: Backoff needs retries
- Cherry-pick onto 1.18: Backoff needs retries
- Cherry-pick onto 1.17: Azure Instance generation changes
- Cherry-pick onto 1.16: Azure Instance generation changes
- Azure: optional jitter on initial VMSS VM cache refresh
- Remove go.mod from local copy of gophercloud
- Fix module path in local gophercloud copy
- Kops - use custom GCS state store for all kops commands
- Azure: Add test scenarios for basic lb + vmss and cluster autoscaler + multiple nodepools.
- add csi-driver-smb test support on kubetest
- azure blobfuse driver rename
- rename blobfuse repo
- Set azure loadbanacer sku to basic when enabling public IP address in agentpool
- Add lb sku env to cloud provider azure e2e tests
- Azure: bump aks-engine version to v0.54.0
- Ensure the pods are ready before creating new pods
- Ensure subnet is deleted
- Switch from azure cli to aks-engine api to deploy clusters
- Delete sudo command to prevent failure
- Move service annotation tests to the corresponding file
- Add aks-engine deploy manifest for basic LB and cluster autoscaler multiple node pool
- Chang lb sku basic to Basic
- Set azure loadbanacer sku to basic when enable public IP address in agentpool
Created an issue in kubernetes/kubernetes that received 1 comment
Kube-controller-manager panic when wrong Azure VMSS name is configured
What happened:
Kube-controller-manager panic when wrong Azure VMSS name is configured:
panic: runtime error: invalid memory address or nil pointer…
1
comment