Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-9191

Refactor the way to retrieve pod logs on managed cluster

XMLWordPrintable

    • Refactor the way to retrieve pod logs on managed cluster
    • False
    • None
    • False
    • Green
    • In Progress
    • ACM-1357 - Management Support of MicroShift devices
    • 0% To Do, 0% In Progress, 100% Done

      OCP/Telco Definition of Done
      https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
      Epic Template descriptions and documentation.
      https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
      ACM-wide Product Requirements (Top-level Epics)
      https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

      *<--- Cut-n-Paste the entire contents of this description into your new
      Epic --->*

      Epic Goal

      Use cluster-proxy addon to retrieve pod logs on the managed cluster.

      Why is this important?

      Currently ACM retrieves pod logs of managed cluster by exposing a service via Route or Loadbalancer on the managed cluster. 

      the cluster-proxy addon has been enabled by default in MCE, so to retrieve the pod logs by cluster-proxy addon will bring more benefits. there is no need to expose service for Hub to access logs on all kinds of managed clusters  even in the on-premise scenarios.

      Scenarios

      As a Cluster Admin:

      • I want to retrieve pod logs from OCP/non-OCP clusters without Route/LoadBalancer.
      • I want to retrieve pod logs from private cluster or on-premise cluster (Hub cluster cannot access the managed cluster directly)

      Acceptance Criteria

      ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      1. ...

      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 - Doc issue opened with a completed template. Separate doc issue
        opened for any deprecation, removal, or any current known
        issue/troubleshooting removal from the doc, if applicable.

            zyin@redhat.com Zhiwei Yin
            zyin@redhat.com Zhiwei Yin
            Hui Chen Hui Chen
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: