Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1688784 - [Doc Wrong] Overview section in Encrypting Data at Datastore Layer
Summary: [Doc Wrong] Overview section in Encrypting Data at Datastore Layer
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Xiaoli Tian
Vikram Goyal
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-14 12:39 UTC by Shivkumar Ople
Modified: 2019-03-15 07:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1686452 None CLOSED Can CustomResources be encrypted in etcd? 2019-03-14 12:39:29 UTC

Description Shivkumar Ople 2019-03-14 12:39:30 UTC
Document URL:

Section Number and Name: Overview Section.

Describe the issue: 

In the overview section, 

This topic reviews how to enable and configure encryption of secret data at the datastore layer. While the examples use the secrets resource, any resource can be encrypted, such as configmaps.

This line states that "any resource can be encrypted, such as configmaps." Here the word ANY is wrong. 
As any resource can't be encrypted only the secret and configmaps can be encrypted according to the recently closed bug(Can custom resources be encrypted in etcd?), attached to this bug.

Suggestions for improvement: Remove "Any" word from the above mentioned line. And keep "resources such as secrets and configmaps can be encrypted only".

Additional information:

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