In EaseMesh, we use easegress a sidecar, it fetches its belonging service's description metadata(not the already handled control logic related data, such as Canary, CircuitBreaker) and stores it into local models,e.g., sidecar's registry module will cache this server's tenant info for further usage.
EaseMesh can update service's description metadata with emctl or API, but this metadata can only be updated if we redeployed this Pod.
Proposal
Using informor to monitor the whole service spec in every module of the sidecar.
Or using Etcd API for every time spec usage.
Or monitor this data and calling K8s API for deleting the older Pod.
benja-wu
commented
2 years ago
Background
tenantinfo for further usage.emctlor API, but this metadata can only be updated if we redeployed this Pod.Proposal
informorto monitor the whole service spec in every module of the sidecar.