apache/apisix

feat: As a user, I want kubernetes service discovery to support more configuration items

Open

#8,311 创建于 2022年11月11日

在 GitHub 查看
 (15 评论) (0 反应) (0 负责人)Lua (16,597 star) (2,860 fork)batch import
good first issue

描述

Description

Recently, we deployed apisix on different clouds and used the feature of kubernetes service discovery. The problem is that on different clouds, the proxy layer (LB) in front of apiserver has different idle timeouts. However, in apisix's kubernetes service discovery, The time of a watch is fixed, which will cause a problem: when there is no endpoints event in the cluster for a long time, the server will time out instead of the client, and then the service discovery will restart the list-watch after a fixed 40 seconds , so if you can add some configuration items, such as the duration of a watch, retry time or strategy, etc., thank you!

贡献者指南

技术栈
无
领域
backendcloud
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Kubernetes service discoveryAPISIX configuration patternsLua programmingList watch mechanism
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
65
研究方向
Investigate the existing Kubernetes service discovery implementation in the APISIX codebase, likely in the `lib/plugins/discovery/` directory. Understand the current fixed watch timeout of 40 seconds and the retry logic. Propose new configuration items such as watch duration and retry timeout. Ensure backward compatibility.