Skip to content

Refactor marke events logic #72

@kaplanelad

Description

@kaplanelad

Description:
StatusBay event flow:

  1. The watcher collect events from multiple resources (pods, deployment, replicaset, daemonset and etc)
  2. All the events saved in DB
  3. The frontend makes a request to get a deployment detail (api/v1/kubernetes/application/{apply_id})
  4. 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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions