Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-8797

[Doc] Enable configuration in Backstage CR for mounting files and injecting env variables into non-backstage-backend containers

XMLWordPrintable

    • [Doc] Enable configuration in Backstage CR for mounting files and injecting env variables into non-backstage-backend containers
    • M
    • False
    • Hide

      None

      Show
      None
    • False
    • RHIDP-8713Enable configuration in Backstage CR for mounting files and injecting env variables into non-backstage-backend containers
    • In Progress
    • RHIDP-8713 - Enable configuration in Backstage CR for mounting files and injecting env variables into non-backstage-backend containers
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      = Customizable container deployment in {product} pods

      Previously, injecting necessary files (`extraFiles`) and environment variables (`extraEnvs`) was restricted to the default `backstage-backend` container.

      With this update, you can configure resource injection for any container in the {product} pod, including sidecars and system containers. This allows you to complete the job of deploying custom components, such as security agents, log collectors, or configuration managers, that require specific volumes or runtime variables to operate successfully.

      See {configuring-book-link}#proc-injecting-custom-files-and-environment-variables-into-backstage-containers[Injecting extra files and environment variables into {backstage} containers].

      // Duplicate of https://issues.redhat.com/browse/RHIDP-8715
      Show
      = Customizable container deployment in {product} pods Previously, injecting necessary files (`extraFiles`) and environment variables (`extraEnvs`) was restricted to the default `backstage-backend` container. With this update, you can configure resource injection for any container in the {product} pod, including sidecars and system containers. This allows you to complete the job of deploying custom components, such as security agents, log collectors, or configuration managers, that require specific volumes or runtime variables to operate successfully. See {configuring-book-link}#proc-injecting-custom-files-and-environment-variables-into-backstage-containers[Injecting extra files and environment variables into {backstage} containers]. // Duplicate of https://issues.redhat.com/browse/RHIDP-8715
    • Feature
    • Rejected

      EPIC Goal

      What are we trying to solve here?

      Background/Feature Origin

      Why is this important?

      User Scenarios

      Dependencies (internal and external)

      Acceptance Criteria

      Release Enablement/Demo - Provide necessary release enablement details and documents
      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 Playwright: <link or reference to playwright>
      QE - Automated tests merged: <link or reference to automated tests>
      DOC - Downstream documentation merged: <link to meaningful PR>

              rhn-support-pabel Priyanka Kantem
              rhdh-jirabot RHDH Jirabot
              RHIDP - Documentation
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: