XMLWordPrintable

    • Pipeline audit logs
    • False
    • None
    • False
    • To Do
    • 100
    • 100% 100%

      Epic Goal

      Enhance pipeline logs to include audit logs. Pipelines logs currently contain the output of the pods executing the pipelines but miss out the events and conditions surrounding the pipeline execution. Therefore, it is challenging to reason on specifics of what went on and for example caused a failure during the pipelinerun execution when looking at past logs for a particular pipelinerun.

      Examples of such events are:

      • TaskRun pod is OOMKilled
      • TaskRun pod cannot get scheduled due to insufficient cpu/mem on the cluster
      • TaskRun pod cannot start due to CrashLoopBackOff

      Why is this important?

      In order to fully capture the details of a pipelinerun execution for audit purposesĀ 

      Acceptance Criteria (Mandatory)

      • Pipelinerun logs are auditable and contain pipelinerun and related taskruns logs, events, other relevant metadata for audit
      • Admin can configure the verbosity of pipelinerun audit logs
      • Release Technical Enablement - Provide necessary release enablement details and documents

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

            Unassigned Unassigned
            ssadeghi@redhat.com Siamak Sadeghianfar
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: