MirtoBusico commented on issue #853:
URL:
https://github.com/apache/apisix-ingress-controller/issues/853#issuecomment-1032916023
@tao12345666333 Sorry it is a real bug. Please reopen
After three or four times that I restart the cluster (it is a lab framework:
start on the morning and shutdown on the night) the route takes a POD address
again.
The same framework used in my previous reply now shows:
Route definition, service addresses and pod addresses
```
sysop@m01serv:~/software/apisisx$ cat productpage-ar.yaml
apiVersion: apisix.apache.org/v2beta2
kind: ApisixRoute
metadata:
name: productpage
spec:
http:
- name: rule1
match:
hosts:
- www2.m01.net
paths:
- /*
backends:
- serviceName: productpage
servicePort: 9080
resolveGranularity: service
sysop@m01serv:~/software/apisisx$ kubectl get svc -n bookinfo
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
details ClusterIP 10.43.230.138 <none> 9080/TCP 13d
ratings ClusterIP 10.43.16.57 <none> 9080/TCP 13d
reviews ClusterIP 10.43.236.52 <none> 9080/TCP 13d
productpage ClusterIP 10.43.189.220 <none> 9080/TCP 13d
sysop@m01serv:~/software/apisisx$
sysop@m01serv:~/software/apisisx$ kubectl get pods -n bookinfo -o wide
NAME READY STATUS RESTARTS AGE IP
NODE NOMINATED NODE READINESS GATES
reviews-v3-5cddf46b56-x2hbz 2/2 Running 10 (9h ago) 9d
10.42.2.210 m01kw2 <none> <none>
details-v1-65fff9896-fw7qv 2/2 Running 10 (9h ago) 9d
10.42.1.244 m01kw1 <none> <none>
reviews-v1-d7f5b879b-bf7tz 2/2 Running 10 (9h ago) 9d
10.42.1.4 m01kw1 <none> <none>
productpage-v1-77748558b4-w2h2h 2/2 Running 10 (9h ago) 9d
10.42.1.2 m01kw1 <none> <none>
ratings-v1-5db74dc944-5z2rz 2/2 Running 10 (9h ago) 9d
10.42.0.17 m01km <none> <none>
reviews-v2-6fcf6d48b4-bvtzn 2/2 Running 10 (9h ago) 9d
10.42.0.23 m01km <none> <none>
sysop@m01serv:~/software/apisisx$
```
The route definition taken from the apisix dashboard:
```
nodes:
- host: 10.42.1.232
port: 9080
weight: 100
type: roundrobin
hash_on: vars
scheme: http
pass_host: pass
name: bookinfo_productpage_9080
desc: Created by apisix-ingress-controller, DO NOT modify it manually
labels:
managed-by: apisix-ingress-controller
```
Clearly the route don't work
I cannot figure out why the address changes.
BTW another route defined using the apisix dashboard continues to work
regularly
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
