Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-668

Better Errata Tracking for RHCOS Phase 1: CVEs

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Major Major
    • openshift-4.14
    • None
    • OS
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 100
    • 100% 100%
    • 0
    • 0
    • Program Call

      Feature Overview (aka. Goal Summary)  

      Today it is not a simple task to track a fix from RHEL into RHCOS releases. Eventually we want it to be easy for customers to understand all changes between versions of RHCOS. First and most important, however, is better notification & tracking of CVE remediation for RHEL components in OCP.

      Goals (aka. expected user outcomes)

      As an OpenShift Container Platform customer I need to be able to determine if my OCP cluster is impacted by a security vulnerability/CVE, and, if so, which OCP updates contains the fix. 

      Currently, Product Security can not track RHEL security vulnerabilities/CVEs that also affect OCP.  Customers do not know that their clusters are impacted.  Shipping the fix in RHEL 8 does not immediately fix it in OCP/RHCOS.  A new build of RHCOS based on the updated packages needs to be made available for each active, supported version of OCP. Even then, if customers don't know they are affected, then they won't know they need to update. 

      The goal for this phase is for RHEL component CVE pages to also track affected RHCOS releases.

            rhn-support-mrussell Mark Russell
            rhn-support-mrussell Mark Russell
            Michael Nguyen Michael Nguyen
            Ashley Hardin Ashley Hardin
            Derrick Ornelas Derrick Ornelas
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: