anchor.diff:  ----
   ====
   
  -As a result, two files will be created: the public key (as explained above) and a
  -corresponding private key (one of `id_dsa`, `id_ecdsa`, `id_ed25519` or
  -`id_rsa`). With both of these in place you should consult your source control
  -management (SCM) system's manual on how to upload the public key. The private
  -key will be used to access your private repository.
  -
  -The
  -https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/design/secrets.md[Secret]
  -resource is used to store your keys. Create the `*Secret*` first before using
  -the SSH key to access the private repository. The `*data*` field for the
  -`*Secret*` object must contain your private key with the value set to the
  -base64-encoded content of that file:
  +Two files are created: the public key and a corresponding private key (one of
  +`id_dsa`, `id_ecdsa`, `id_ed25519`, or `id_rsa`). With both of these in place,
  +consult your source control management (SCM) system's manual on how to upload
  +the public key. The private key will be used to access your private repository.
  +
  +A link:dev_guide/secrets[`*secret*`]
  +is used to store your keys.
  +
  +. Create the `*secret*` first before using the SSH key to access the private
  +repository:
  ++
  +====
  +----
  +$ osc create -f secret.json
  +----
  +====
  +
  +. The `*data*` field for the `*secret*` must contain your private key with the
  +value set to the base64-encoded content of that file:
   
   ====
   
  
positive.code: 
  You can define multiple Docker registry entries in this file. Alternatively, you
  can also add authentication entries to this file by running the `docker login`
  command. The file will be created if it does not exist.
  
  Kubernetes provides the https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/design/secrets.md[Secret]
  resource, which is used to store your configuration and passwords.
  
  To create the `*Secret*` resource from your local `.dockercfg` file, you can run
  following command:
  
  ====
  ----
  $ oc secrets new dockerhub ~/.dockercfg
  ----
  ====
  
  This command generates JSON specification of the Secret resource named
  'dockerhub' and creates the object.
  
  Once you have created your Secret, it must be added to the builder service account
  in order to be used.
  
  ====
  ----
  $ oc secrets add serviceaccount/builder secrets/dockerhub
  ----
  ====
  
  Once you have the `*Secret*` created, you can add a `PushSecret` field into the
  `Output` section of the `BuildConfig` and set it to the name of the `*Secret*`
  that you created, which in the above example is `*dockerhub*`:
  
  ====
  
  ----
  
negative.code: ----
  ====
  
  . Create a second `*secret*` for Docker from the *_secret.json_* file:
  +
  ====
  
  ----
  