RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1315917 - [RFE] Support exposing secret keys in environment variables
Summary: [RFE] Support exposing secret keys in environment variables
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kubernetes
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Chaloupka
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-09 01:21 UTC by Kenjiro Nakayama
Modified: 2019-11-14 07:34 UTC (History)
2 users (show)

Fixed In Version: kubernetes-1.2.0-0.10.git738b760.el7
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 14:52:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1032 0 normal SHIPPED_LIVE kubernetes bug fix and enhancement update 2016-05-12 18:51:14 UTC

Description Kenjiro Nakayama 2016-03-09 01:21:55 UTC
1. Proposed title of this feature request

Support exposing secret keys in environment variables

2. Who is the customer behind the request?

(In private)

3. What is the nature and description of the request?

Exposing secret keys in environment variables has been supported after the release upstream kuberentes v1.2.0-alpha.7. The customer needs the feature in RH's kubernetes package.

4. Why does the customer need this? (List the business requirements here)

The feature will allow their Kubernetes cluster to be compliant with security, allowing secure management of containers including authorization and credentials of communications with their external systems.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

No. But it has already implemented in upstream.

Report: https://github.com/kubernetes/kubernetes/issues/4710
PR    : https://github.com/kubernetes/kubernetes/pull/18298

*NOTE* It contains kubernetes v1.2.0-alpha.7.

9. Is the sales team involved in this request and do they have any additional input?

No.

10. List any affected packages or components.

kubernetes
kubernetes-client
kubernetes-master
kubernetes-node

Comment 10 errata-xmlrpc 2016-05-12 14:52:37 UTC
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://rhn.redhat.com/errata/RHEA-2016-1032.html


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