feat: As a user, I want kubernetes service discovery to support more configuration items · apache/apisix#8311

(15 comments) (0 reactions) (0 assignees)Lua (16,597 stars) (2,860 forks)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
Issue 種別: feature
難度: 3
推定時間: 1-3 hours
活動状況: active
明確さ: clear
前提条件: Kubernetes service discoveryAPISIX configuration patternsLua programmingList watch mechanism
初心者向け度: 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.