anchor.diff:  - Dependency management *(for maven based projects)*
   - Auto align with Docker Registry
   - Enrichers for:
  -    - Kubernetes/Openshift client
  -    - Pods
  -    - Replication Controllers
  -    - Services
  +    ** Kubernetes/Openshift client
  +    ** Pods
  +    ** Replication Controllers
  +    ** Services
   - Integration with Fabric8 Modules:
  -    - link:https://fabric8.io/guide/mavenPlugin.html[Fabric8 Maven Plugin]
  -    - link:https://fabric8.io/guide/fabric8DevOps.html[Microservices Platform]
  +    ** link:https://fabric8.io/guide/mavenPlugin.html[Fabric8 Maven Plugin]
  +    ** link:https://fabric8.io/guide/fabric8DevOps.html[Microservices Platform]
   - "Bring your own client" support
   
   === Pre-requisites
  
positive.code: 
  So what exactly is your test case going to test?
  
  The test cases are meant to consume and test the provided services and assert that the environment is in the expected state.
  
  The test case may obtain everything it needs, by accessing the Kubernetes resources that are provided by the plugin as @ArquillianResources (see resource providers below).
  
  === Resource Providers
  
  
negative.code: Arquillian Cube Kubernetes and Openshift modules, heavily rely on the Fabric8 Kubernetes/Openshift client.
  This client is also used in wide range of frameworks, so its not that long of a shot to encounter version conflicts.
  
  To eliminate such issues, arquillian as of 1.1.0 is using a shaded uberjar of the client which contains versioned
  package (with major and minor version).
  
  All enrichers provided by the arquillian modules, are configured to work both with the internal types, but also with
  whatever version of the client that is found in the classpath.
  
  NOTE: If your existing tests don't have a dependency to the kubernetes-client, you will either need to add
  kubernetes-client, to your classpath or use the internal classes. It is recommended to do the first.
  