Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-495

Dependent operators installation

    • netobserv-dependent-operators
    • False
    • None
    • False
    • Not Selected
    • To Do
    • Impediment
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      Status: Code review

       

      We have all PRs in review for loki and kafka and this is expected to merge by the end of this sprint.

       

      We have some follow on work to do to look at Prometheus and Grafana in subsequent releases 

      Show
      Status: Code review   We have all PRs in review for loki and kafka and this is expected to merge by the end of this sprint.   We have some follow on work to do to look at Prometheus and Grafana in subsequent releases 

      Follow-up on NETOBSERV-193 and on PoC NETOBSERV-219

      As part of 4.12 goals, we want to have loki & strimzi installed as part of the operator installation.
      This work is already done via NETOBSERV-219 (not merged, probably some rebase to do), however, at the moment we don't want to include prometheus and grafana (this is not in 4.12 target / downstream operator goals), so I would recommend to split in two different tasks / PRs, and start with only loki+strimzi.

      We should make the subscriptions optional / configurable, for instance, by externalizing them via yaml files. We can possibly use go embed to integrate these files into the code, if necessary. The goal is to have different subscriptions depending on if it's an upstream or downstream build.

            Unassigned Unassigned
            jtakvori Joel Takvorian
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: