Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1320719 - [RFE] Expose secret keys in environment variables
[RFE] Expose secret keys in environment variables
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.2.0
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Andy Goldstein
DeShuai Ma
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-23 15:50 EDT by Eric Rich
Modified: 2016-05-12 12:33 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-12 12:33:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1064 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 3.2 security, bug fix, and enhancement update 2016-05-12 16:19:17 EDT

  None (edit)
Description Eric Rich 2016-03-23 15:50:07 EDT
Description of problem:

Expose secrets to containers in environment variables:  it should be possible to expose secrets to containers as environment variables. While this is arguably not the optimal way to consume secrets, it will be important to users taking their first steps into a cloud environment, and we should offer this feature to enable a good experience for users who need it.
Comment 2 Qixuan Wang 2016-03-24 09:36:59 EDT
Tested on devenv-rhel7_3820 (openshift v1.1.4-255-g8435563, kubernetes v1.2.0-36-g4a3f9c5, etcd 2.2.5), the bug has been fixed, thanks.

Here are result:
[root@ip-172-18-8-106 home]# oc logs secret-env-pod | grep MY_SECRET_DATA
MY_SECRET_DATA=value-1
Comment 4 errata-xmlrpc 2016-05-12 12:33:53 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2016:1064

Note You need to log in before you can comment on or make changes to this bug.