Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-2447

RFE log forwarding operator supported on other kubernetes platforms, e.g. EKS

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Log Collection
    • RFE log forwarding operator supported on other kubernetes platforms, e.g. EKS
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • NEW
    • To Do
    • NEW

      Goals

      RHACM is looking for a consistent solution for forwarding logs to a central location for all managed clusters, not just OCP.   The operator, based on vector, which can be deployed and configured via ACM is a great solution.  However, if it is OCP-only, then it becomes less interesting.

      A prioritized list of Non-OCP would be: EKS, AKS, GKE, IKS. (note: Anything beyond that, we might move to a support statement based on 'CNCF Kubernetes conformance').

      Non-Goals

      Motivation

      ACM provides management for OCP and Non-OCP. We want to provide a consistent method for log forwarding across the managed fleet.  ACM is the heart of OpenShift Platform Plus, which is the primary sales motion for OCP today.

      Alternatives

      Acceptance Criteria

      Risk and Assumptions

      Documentation Considerations

      Open Questions

      Additional Notes

      Alan Conway:
      Not yet, but it easily could be. The OCP-specific dependencies are minimal, but we never bothered to clean them up because we never had to. If it's of interest we should create an RFE so we can prioritize & schedule.
      It is something we have considered in the past but never had the motivation to do it.

              Unassigned Unassigned
              sberens@redhat.com Scott Berens
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: