Skip to content

Separate inventory build and api  #246

Description

@richardtief

To make the vrops inventory data always accessible for the collectors, the current build and refresh of the inventory should be separated from the api delivery. If there is any error in the inventory build or refresh, the API should remain reachable. The API pod could have multiple replicas in Kubernetes because it is stateless.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions