Bug 1296604

Summary: Usage of Secrets and Certificates to either Access external resources or Secure OSE Services
Product: OpenShift Container Platform Reporter: Greg Hoelzer <ghoelzer>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED NOTABUG 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   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-30 14:19:05 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 Greg Hoelzer 2016-01-07 16:03:12 UTC 
Some of the install/post-install steps such as integrating to an internal Github or other SCM repo, and how Secrets are used with example JSON/YAML on how this would be added to a BuildConfig would be very helpful.   This required a lot of trial and error the first time this was attempted at the Target account.

Additionally, specific examples of how Secrets are exposed as volumes, directories, and files on the target container would be very helpful as customers immediately move away from Environment variables in DeploymentConfigs for Certificates, and User ID/Passwords to connect to external (Non-OSE) services.  Because this wasn't clearly understood or documented at the Target account, the App Dev team created their own implementation for this which basically replicates these features we already provide out of the box.