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.