alibaba / alibaba/alibaba-load-balancer-controller
warning: can not find correspond node
- Dominant language
- Go
- Stars
- 33
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
The service creates a loadbalancer, but targets are empty. I see the following logs:
```
I0409 11:58:03.937777 1 node_utils.go:124] node izj6cikhraaok2ccadccd6z not found
I0409 11:58:03.937799 1 server_groups.go:506] controller/nlb-controller "msg"="warning: can not find correspond node izj6cikhraaok2ccadccd6z for endpoint 192.168.7.166" "service"="nginx-ingress/nginx-ingress-ingress-nginx-controller"
```
Here is my setup
```
- command:
- /load-balancer-controller
- --cloud-config=/etc/kubernetes/config/cloud-config.conf
- --controllers=service
- --leader-elect-resource-name=nlb
- --configure-cloud-routes=false
```
```
apiVersion: v1
kind: Service
metadata:
annotations:
service.beta.kubernetes.io/alibaba-cloud-loadbalancer-zone-maps: "cn-hongkong-d:vsw-xxx,cn-hongkong-c:vsw-xxx"
service.beta.kubernetes.io/alibaba-cloud-loadbalancer-address-type: "intranet"
name: nginx-lb
spec:
externalTrafficPolicy: Local
ports:
- port: 80
targetPort: 80
selector:
app: nginx
loadBalancerClass: "alibabacloud.com/nlb"
type: LoadBalancer
```
Contributor guide
Research direction
Read node_utils.go around line 124 and server_groups.go around line 506, then reproduce the issue with the provided controller flags and Service manifest. Done means explaining why node izj6cikhraaok2ccadccd6z is not matched to endpoint 192.168.7.166 and confirming that the LoadBalancer receives targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100