anchor.diff:  - To use kubernetes extension, your host should have running kubernetes cluster.
   - To use openshift extension, your host should have running openshift cluster.
   
  +=== Setup
  +
  +To use Kubernetes extension you need to register next dependency in your build tool: `org.arquillian.cube:arquillian-cube-kubernetes:${version}`.
  +
  +To use OpenShift extension you need to register next dependency in your build tool: `org.arquillian.cube:arquillian-cube-openshift:${version}`.
  +
   === Configuring the extension
   
   The plugin can be configured using the traditional arquillian.xml, via system properties or environment variables
  
positive.code: 
  ==== Openshift Configuration Parameters
  
  [cols="2,1,1,3", options="header"]
  |===
  | Option                              | Type           | Env | Description                                                   
  
negative.code: 
  Or just setting the following System Properties:
  `-Dsun.net.spi.nameservice.provider.1=dns,ArquillianCubeNameService -Dsun.net.spi.nameservice.provider.2=default`
  
  ==== OpenShift Annotations
  
  OpenShift extension comes with some annotations that let you define resources at test level instead of globally.
  
  ===== `@Template`
  
  A template describes a set of objects that can be parameterized and processed to produce a list of objects for creation by OpenShift.
  
  You can set template location as configuration parameter or using `@Template` annotation at class level.
  
  You can see an example of template usage at https://github.com/arquillian/arquillian-cube/blob/master/openshift/ftest-template-standalone/src/test/java/org/arquillian/cube/openshift/standalone/HelloWorldTemplateTest.java
  
  ===== `@OpenShiftResource`
  
  You can apply OpenShift resources files before test execution.
  These resources creation are meant to be used for resources that aren't tied to a living thing.
  Examples of these are service accounts, credentials, routes, ...
  
  The value can either be:
  
  * link (https://www.github.com/alesj/template-testing/some.json)
  * test classpath resource (classpath:some.json)
  * or plain content ({"kind" : "Secret", ...}
  
  You can use `@OpenShiftResource` either at class level which implies that resource is created before test class execution and they are deleted after class execution or at method level which implies that resources are created and deleted after each test method execution.
  
  You can see an example of OpenShift resources usage at https://github.com/arquillian/arquillian-cube/blob/master/openshift/ftest-openshift-resources-standalone/src/test/java/org/arquillian/cube/openshift/standalone/HelloWorldOpenShiftResourcesTest.java
  
  === Namespaces
  
  