Bug 1305572

Summary: [docs] kibana - provide more details about secrets
Product: OpenShift Container Platform Reporter: Evgheni Dereveanchin <ederevea>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED CURRENTRELEASE QA Contact: Vikram Goyal <vigoyal>
Severity: unspecified Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.1.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://access.redhat.com/documentation/en/openshift-enterprise/3.1/installation-and-configuration/chapter-17-aggregating-container-logs#pre-deployment-configuration
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-30 14:39:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Evgheni Dereveanchin 2016-02-08 15:39:13 UTC 
Document URL: 
https://access.redhat.com/documentation/en/openshift-enterprise/3.1/installation-and-configuration/chapter-17-aggregating-container-logs#pre-deployment-configuration

Section Number and Name: 
 17.2. PRE-DEPLOYMENT CONFIGURATION
  step 2

Describe the issue: 
The document states that "A set of files can be supplied in the secret" suggesting that they are optional. However there's no documentation on whether this step could be skipped or how to proceed without generating any certificates. There's a link to secrets documentation that also has no information about how to create an "empty secret"

Suggestions for improvement: 
Describe a fast way to proceed without generating actual secrets, for example:
$ oc secrets new logging-deployer nothing=/dev/null
If the step is not actually required, state this at the beginning.
Comment 1 Vikram Goyal 2017-12-30 14:39:41 UTC 
This was added just before step 6: https://access.redhat.com/documentation/en-us/openshift_enterprise/3.1/single/installation_and_configuration/index#pre-deployment-configuration

Closing this bug.