-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apisix upsteam node cannot be deleted dynamically #20
Comments
@gxthrj do you have time to look at this? |
@flyingfish7 |
ingress log : curl http://apisix-gw-lb:9080/apisix/admin/upstreams/00000000000000000102/nodes{"node":{"value":{"nodes":{"172.30.118.1:8102":100,"172.30.118.19:8102":100,"172.30.118.3:8102":100,"172.30.118.36:8102":100,"172.30.88.166:8102":100,"172.30.88.153:8102":100,"172.30.88.177:8102":100,"172.30.88.159:8102":100,"172.30.118.6:8102":100,"172.30.88.185:8102":100,"172.30.88.155:8102":100,"172.30.118.55:8102":100,"172.30.88.158:8102":100,"172.30.88.151:8102":100,"172.30.118.48:8102":100,"172.30.118.22:8102":100,"172.30.88.136:8102":100,"172.30.88.179:8102":100,"172.30.118.62:8102":100},"id":"00000000000000000102","hash_on":"vars","key":"/apisix/upstreams/00000000000000000102","desc":"mall_ebs-pc-rest_8102","type":"roundrobin"},"createdIndex":1985,"key":"/apisix/upstreams/00000000000000000102","modifiedIndex":1985},"action":"get"} |
Currently ingress-controller does not support APISIX v1.4.*, because the version does not support |
I tried apisix1.3 and 1.5 version, but the following error will still appear in ingress! E0806 02:40:41.250639 1 builder.go:181] solver upstream failed, update upstream to etcd failed, err: http patch failed, url: http://apisix-gw-lb:9080/apisix/admin/upstreams/00000000000000000086, err: status: 400, body: {"error_msg":"invalid configuration: property "nodes" validation failed: expect object to have at least 1 properties"} |
we can fix this case in APISIX, make it support the number of the upstream node can be |
If Apache APISIX do not support this feature, we can do some protect. |
Close this issue now , we have support the feature the number of upstream node can be 0. Feel free to reopen if you have any question. |
My configuration information is as follows
apisixroute Configuration:
apiVersion: v1
items:
kind: ApisixRoute
metadata:
creationTimestamp: "2020-07-17T05:51:42Z"
generation: 7
name: mall-apisix-ingress
namespace: mall
resourceVersion: "2771827"
selfLink: /apis/apisix.apache.org/v1/namespaces/mall/apisixroutes/mall-apisix-ingress
uid: 357ffbad-97d1-4f28-b801-247a46b4b226
spec:
rules:
http:
paths:
serviceName: ebs-app-rest
servicePort: 8100
path: '*'
[root@m1 apisix-ingress]# kubectl describe svc ebs-app-rest -n mall
Name: ebs-app-rest
Namespace: mall
Labels:
Annotations: kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"name":"ebs-app-rest","namespace":"mall"},"spec":{"ports":[{"name":"http"...
Selector: app=ebs-app-rest
Type: ClusterIP
IP: 10.254.199.108
Port: http 8080/TCP
TargetPort: 8100/TCP
Endpoints: 172.30.88.170:8100
Session Affinity: None
Events:
172.30.88.169,172.30.88.143 is not automatically deleted!
How to solve the problem!
The text was updated successfully, but these errors were encountered: