Uploaded image for project: 'OpenShift Node'
  1. OpenShift Node
  2. OCPNODE-2004

Log linking by default in CRI-O

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Duplicate
    • Icon: Critical Critical
    • openshift-4.16
    • None
    • None
    • None
    • Log Linking by Default in CRI-O
    • False
    • None
    • False
    • Not Selected
    • To Do

      Epic Goal

      • Allow log linking by default, instead of requiring a user to add a custom MC

      Why is this important?

      • log linking should be available on hosted control planes and having custom MCs isn't a sustainable solution for that architecture.

      Scenarios

      1. as an openshift admin, I'd like access to the log linking feature without custom MC

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              pehunt@redhat.com Peter Hunt
              pehunt@redhat.com Peter Hunt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: