Refactor marke events logic
Opened this issue · 0 comments
kaplanelad commented
Description:
StatusBay event flow:
- The watcher collect events from multiple resources (pods, deployment, replicaset, daemonset and etc)
- All the events saved in DB
- The frontend makes a request to get a deployment detail (api/v1/kubernetes/application/{apply_id})
- The API get the row from the DB, and loop on all the resources kind for check the event content (for marke suspects events )
File: api/kubernetes/markevent.go
Function: MarkApplicationDeploymentEvents
Problem:
The current implementation is not generic enough when we add more resources kind's we need to modify this function + we have a reputable code.
Definition Of Done:
Support automatically multiple resources kind that added into StatysBay
Move reputable code to function