Uploaded image for project: 'Docs for Red Hat Developers'
  1. Docs for Red Hat Developers
  2. RHDEVDOCS-3000

Document: Build Resource Volume Mounts




      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

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

      Epic Goal

      • Allow ConfigMaps and Secrets (resources) to be mounted as volumes in a build

      Why is this important?

      • Secrets and ConfigMaps can be added to builds as "source" code that can leak into the resulting container image
      • When using sensitive credentials in a build, accessing secrets as a mounted volume ensure that these credentials are not present in the resulting container image.


      1. Access private artifact repositories (Artifactory, jFrog, Mavein)
      2. Download RHEL packages in a build

      Acceptance Criteria

      • Builds can mount a Secret or ConfigMap in a build
      • Content in the secret or ConfigMap are not present in the resulting container image.

      Dependencies (internal and external)

      1. Buildah - support mounting of volumes when building with a Dockerfile

      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>




            rdlugyhe Rolfe Dlugy-Hegwer
            rdlugyhe Rolfe Dlugy-Hegwer
            xiujuan wang xiujuan wang
            0 Vote for this issue
            1 Start watching this issue