anchor.diff:  ----
   skipper:>status --release-name helloworldk8s
   ╔═══════════════╤══════════════════════════════════════════════════════════════════════════════════════╗
  -║Last Deployed  │Wed Oct 25 12:31:49 EDT 2017                                                          ║
  +║Last Deployed  │Wed Oct 25 17:34:24 EDT 2017                                                          ║
   ║Status         │DEPLOYED                                                                              ║
   ║Platform Status│The applications are being deployed.                                                  ║
  -║               │helloworldk8s-helloworld-docker-v1[helloworldk8s-helloworld-docker-v1-8wghk=deploying]║
  +║               │helloworldk8s-helloworld-docker-v1[helloworldk8s-helloworld-docker-v1-g8j39=deploying]║
   ╚═══════════════╧══════════════════════════════════════════════════════════════════════════════════════╝
   ----
   
  
positive.code: More flexible upgrade strategies are planned along with the introduction of the https://projects.spring.io/spring-statemachine/[Spring Cloud State Machine] project to orchestrate the update process.
  
  
  To get the URL of this app on minikube
  
  ----
  $ minikube service --url helloworldk8s-helloworld-docker-v1
  http://192.168.99.100:32123
  ----
  
  
  
negative.code:     spring.cloud.deployer.kubernetes.createNodePort: 32123
  ----
  
  The manifest is in a Kubernetes Resource file inspired format.  By looking at the manifest you can see which Docker images was used and which properties were set before the final push to Kubernetes.
  The metadata values that are present will be used in the next release to support searching for releases based on those values.
  
  Since it is somewhat awkward to specify multiple flattened out YAML values for the `--properties` argument in the shell, you can also specify the location of a YAML file when installing or upgrading.
  