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

Only allow signed images to be running in OpenShift system namespaces

XMLWordPrintable

    • Product / Portfolio Work
    • None
    • 100% To Do, 0% In Progress, 0% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Feature Overview (aka. Goal Summary)  

      Leverage ImagePolicy definitions in all OpenShift core system namespaces to enforce that only pods with Red Hat-signed OpenShift images can be run there.

      Goals (aka. expected user outcomes)

      This will add an additional layer of security that goes beyond enforcing that images from official Red Hat product registries need to have a valid signature but also that in vital core namespaces of OpenShift only such images can be executed. This protects from attacks against the core payload index image or malicious users attempting to launch workloads in OpenShift core namespaces to exilftrate information.

      Requirements (aka. Acceptance Criteria):

      • a wild-card pattern in the scope property of (Cluster)ImagePolicy that enforces the signature validation for any image
      • ImagePolicy instances in all OpenShift core-namespaces that are scoped to any image having to pass verification against the Red Hat signing key
      • a capability to turn off these policies, e.g. for troubleshooting

       

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both both
      Classic (standalone cluster) yes
      Hosted control planes yes
      Multi node, Compact (three node), or Single node (SNO), or all all
      Connected / Restricted Network both
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) all
      Operator compatibility n/a
      Backport needed (list applicable versions) n/a
      UI need (e.g. OpenShift Console, dynamic plugin, OCM) n/a
      Other (please specify)  

      Customer Considerations

      Before the customer updates to a cluster version enforcing these policies a preflight update check must exist that warns the user about any custom pods in these namespaces that would not be restarted after the cluster update.

              Unassigned Unassigned
              DanielMesser Daniel Messer
              None
              None
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: