XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • korrel8r-operator
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • NEW
    • If Release Note Needed, Set a Value

      Goals

      Create a stand-alone operator  to deploy korrel8r as a service in an openshift cluster, with a defaut configuration to connect to all available default stores.

      Upstream issue: https://github.com/korrel8r/korrel8r/issues/54

      CRD Spec should use types from https://github.com/korrel8r/korrel8r/blob/main/pkg/config/types.go

      CRD status should report errors in configuration and connecting to stores.

      Non-Goals

      Nothing special

      Motivation

      Need to install korrel8r independently, it interacts with many other components.

      May become part of a future "observability operator" when that is defined.

      Alternatives

      None known

      Acceptance Criteria

      • Deploy korrel8r from operatorhub
      • Provide deployment configuration to connect to
        • Default lokistack for logs
        • Openshift prometheus
        • Openshift alert manager
        • ... others when supported by korrel8r
      • If some stores are not available, korrel8r should function but warn in its status.

      Risk and Assumptions

      Nothing special

      Documentation Considerations

      • Doc for korrel8r itself, based on upstream doc: https://korrel8r.github.io/korrel8r
      • CRD self-documentation and OperatorHub doc in API comments
      • Documentation of default configuration (can we make this a self-documented "required resource" on operatorhub?)

      Open Questions

      What are the appropriate service accounts and roles for korrel8r itself and for korrel8r clients? Provides access to wide range of observability data.

      Additional Notes

            Unassigned Unassigned
            rhn-engineering-aconway Alan Conway
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: