1. Proposed title of this feature request Environment Variables in BuildConfig 3. What is the nature and description of the request? "I want to set an environment variable from a secret in a Build Config" 4. Why does the customer need this? (List the business requirements here) Customer wants to be able to set secure information like passwords into environment variables, and does not want them as plaintext outside of the pod (thus needs the secret) 5. How would the customer like to achieve this? (List the functional requirements here) They want to set in buildconfig something like: strategy: sourceStrategy: env: - name: MAVEN_OPTS valueFrom: secretKeyRef: key: mvnopts name: mvnopts Currently when doing this they get: * spec.strategy.sourceStrategy.env[2].valueFrom: Invalid value: {"secretKeyRef":{"Name":"mvnopts","key":"mvnopts"}}: valueFrom is not supported in build strategy environment variables 6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Make a bc referencing a secret for valueFrom 7. Is there already an existing RFE upstream or in Red Hat bugzilla? http://kubernetes.io/docs/user-guide/secrets/#using-secrets-as-environment-variables 10. List any affected packages or components. builds, secrets
Should also support config map references; currently fails with similar error: (spec.strategy.dockerStrategy.env[1].valueFrom: Invalid value: {"configMapKeyRef":{"Name":"name","key":"key"}}: valueFrom is not supported in build strategy environment variables Works for standard env values, i.e. spec.strategy.dockerStrategy.env[1].value
That is covered in the referenced trello card.
Would you have any updates regarding this feature request?
for everything except pipeline strategies, this is being delivered as part of v3.6.