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

Facilitate the installation steps (4.11)

    • netobserv-facilitate-install
    • True
    • This epic was automatically marked as blocked because the resolution for a subtask has been set to Won't Do (or Won't Fix), indicating a functional team cannot support this epic.
    • False
    • To Do
    • Impediment
    • 0% To Do, 0% In Progress, 100% Done
    • L

      Installing the netobsver operator requires to follow a bunch of steps currently. Some of them (if not all) could be automated. A basic, "demo" deployment for Loki and Kafka could also be provided optionally.

      Steps that could be automated:

      • For upstream ovn-kubernetes, patching OVN daemonset to enable IPFIX (this epic, 4.11)
      • Patching console operator cluster resource to register plugin (this epic, 4.11)
      • Installing Loki (next epic NETOBSERV-495, 4.12)
      • Installing Grafana (post-poned)
      • When implemented, install Kafka (next epic NETOBSERV-495, 4.12)

      The last 3 items can be provided for demo purpose only but we must make it clear that we are not supporting these products, and this is not the way to go for fine-tuning production environment (for instance, we will not replicate the work done with the Loki operator, or with Strimzi, we won't incorporate all the options that could be found in their respective operators.)

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

              Created:
              Updated:
              Resolved: