Initial secret information added

[bfallonf]

@pmorie As discussed. This is info grabbed from the upstream docs and other PRs. A few things:

1. I put in an example json. It can always be taken out if a yaml is better in your opinion.
2. Is the "Creating Secrets" part correct? Did I see somewhere there are actualt oc secret command? Can't re-find.
3. A lot of the information you defined in your skeleton is missing. Is there anything you can help fill in? Or maybe other places I get that info from?
4. The examples you listed here don't match the examples in the upstream doc. Is that on purpose? Wondering if the upstream examples are not viable use cases, and your suggestions are.

Thanks.

[pmorie]

There is actually an exception to this -- since secret data does not come to rest on the node, if the node is rebooted, the secret data must be re-read from the API server.

[pmorie]

@bfallonf @adellape IMO this is a great start. @adellape feel good about merging?

[adellape]

@pmorie It brings me great pleasure to merge. I'll do a quick follow-up PR to actually get it into the buildcfg, and to fix a broken link.

[adellape]

@bfallonf BTW per your question in the PR's initial comment, use YAML instead of JSON when you can.

[pmorie]

@adellape i knew i had missed something re: buildconfig

[adellape]

@pmorie Putting it together atm, no worries.

[adellape]

Followed up in #576.