anchor.diff:  ----
   
   == Bind to a reproducible IP
  -In systems like linux or mac, you can create an link-local interface, with an static ip, that you can reuse in any place you go. There's a system environment variable
  +In systems like linux or mac, you can create a link-local interface, with a static ip, that you can reuse in any place you go. There's a system environment variable
   that you can define to use this ip to bind the cluster to. Otherwise it will default to 127.0.0.1
   
   Example: 
  
positive.code: oc-cluster down  
  oc-cluster up workshop        # Brings up a cluster named workshop
  oc-cluster down
  oc-cluster up java-cluster    # Brings up again my java-cluster with all the info I had in there before
  oc-cluster down
  ----
  
  As you've realised the clusters by default are persistent. That means that you can create as many clusters (profiles) as you
  want, and bring them up and down at will. But what do I do once I'm finished with a cluster? For that there is *cluster management lifecycle*.
  
  == Cluster management lifecycle
  Again, we'll use some examples to ilustrate:
  
negative.code: https://127.0.0.1:8443/console
  ----
  
  I need to log in to the origin container, to check something:
  
  ----
  $ oc-cluster ssh
  