apache/apisix

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

Open

Aperta il 11 nov 2022

Vedi su GitHub
 (15 commenti) (0 reazioni) (0 assegnatari)Lua (16.597 star) (2860 fork)batch import
good first issue

Descrizione

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!

Guida contributor

Tech stack
Nessuno
Dominio
backendcloud
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
active
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Kubernetes service discoveryAPISIX configuration patternsLua programmingList watch mechanism
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
65
Direzione di ricerca
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.