- What is the nature and description of the request? 
We would like to consume namespace or project labels via the downward API in Containers through environment variables. Mapping labels to environment variables is currently not supported (https://docs.openshift.com/container-platform/3.3/dev_guide/downward_api.html#selecting-fields)

- Why does the customer need this? (List the business requirements here) 
It will be very interesting to make the provided images better parameterizable. Often, it will be the platform provider that wants to provide parameterization via project / namespace labels. 
One use case for this is the Java/Maven S2I builder image. As a platform provider, we would like to provide & configure project specific library repositories. To make it convenient for developers, we would like to provide the URL to the various repositories (proxy, snapshot, release) through labels on the project. Any builder image that is interested in this information could declare this, and would get these variables "injected". If OpenShift would standardize on certain variables, OpenShift images could even be prepared for this case, so that customer platform admins don't need to re-build the OpenShift provided images just to add this level of build support.

- How would the customer like to achieve this? (List the functional requirements here) 
We envisage that it should be quite simple to extend the current mechanism to support this scenario. Instead of just referring to "label", one should be able to navigate into the label section by naming labels:
      env:
        - name: RELEASE_REPO_URL
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace.labels:mycompany.com/maven_release_repo_url

- Is there already an existing RFE upstream or in Red Hat Bugzilla?
Unclear but could not find anything