GreatLiu

Results 8 issues of GreatLiu

一、现象 1. 循环请求某个接口 ```shell while true;do echo; sleep 1s; date +%s; curl -s -w '%{time_namelookup}:%{time_connect}:%{time_starttransfer}:%{time_appconnect}:%{time_pretransfer}:%{time_redirect}:%{time_total}:%{http_code}' http://xxx.yyy.com/longtail/anchorPost;done ``` 2. 偶现3s超时 ![image](https://user-images.githubusercontent.com/7006014/162691992-c103947b-d2ce-463f-9cf2-da2d8c030a4e.png) 3. 通过抓包偶现tcp三次握手异常 ![image](https://user-images.githubusercontent.com/7006014/162692556-7b8b9bd5-c412-41ef-9d57-5f08ea2fb9f5.png) 二、dpvs配置 1. lanip配置 ![image](https://user-images.githubusercontent.com/7006014/162693003-936dd5a9-0329-47ba-887e-8a9018457f6f.png) 2. vip配置 ![image](https://user-images.githubusercontent.com/7006014/162693221-2d958d72-fca8-4615-9d8f-f3843b2468d4.png)...

issue/to-reproduce

目前我们线上用的是lvs-dr+ospf的模式,lvs的性能监控用的是node_exporter采集数据,prometheus收集数据,grafana展示数据;realserver的监控检查用的是keepalived的功能,keepalived屏蔽了vrrp的功能,不知道dpvs性能监控及realserver健康检查采用的是什么方案

后端实例ip+port不需要人为配置,直接从注册中心根据相关前缀key获取,可以支持常用的注册中心,比如:etcd、zk、eureka、nacos等

enhancement

### Issue description 1. apisix-ingress-controller控制台日志有大量service not found ``` 2022-08-09T15:24:19+08:00 info ingress/controller.go:606 service kube-system/kube-scheduler not found ``` 2. helm包value.yaml文件仅配置如下命名空间 ![image](https://user-images.githubusercontent.com/7006014/183590010-ca8696d7-9a7c-4c59-b741-fb5b73a22711.png) 3. 通过分析源码有过滤命名空间的逻辑 ![image](https://user-images.githubusercontent.com/7006014/183589479-2cc961cb-dd06-4900-a511-2e457d0bb74f.png) ![image](https://user-images.githubusercontent.com/7006014/183589117-244af1ce-efe7-4f36-9c0c-10438a3d1498.png) 问题:为什么会watch 其他的命名空间的资源,不解? ### Environment - your apisix-ingress-controller...

question

### Issue description ## 问题1: 1. admin api根据id获取upstream json数据如下: ![image](https://user-images.githubusercontent.com/7006014/182865884-04b00294-743f-4cf7-a00b-a70ba132f5c2.png) 2. apisix-ingress-controller定义的数据结构如下: ![image](https://user-images.githubusercontent.com/7006014/182844021-7ca224b3-87df-4624-a3a4-e36202d8d221.png) 3. 注释红框中的判断,否则解析报错 ![image](https://user-images.githubusercontent.com/7006014/182866463-7d81a63b-8cb7-4efe-8a47-1cef40fa94fb.png) 3.1 不注释代码的情况下,报错: ``` 2022-08-04 22:04:55.984 error unexpected non-empty object ``` 3.2 注释代码的情况下,upstreamNode解析为空: ``` &{Metadata:{ID:419230261889204925...

area/controller
triage/accepted

### Issue description 如果apisix是新集群且没有任何apisix对象,controller启动时list所有apisix的对象,会出现404报错,导致controller无法初始化完成 ![image](https://user-images.githubusercontent.com/7006014/184871757-c05e1a4b-9178-46e9-9ab4-8c4cf1f44983.png) ![image](https://user-images.githubusercontent.com/7006014/184871798-76c543a7-5095-4721-8498-34f0a118d52f.png) ### Environment - your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.4.1 - your Kubernetes cluster version (output of kubectl version): 1.16 - if...

question

Please answer these questions before submitting a pull request, **or your PR will get closed**. **Why submit this pull request?** - [x] Bugfix - [ ] New feature provided -...

控制面支持不同粒度的开启插件功能,比如:API级、消费者级等