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.