anchor.diff:  
   (You can use any custom URL provided the appropriate URL stream handler.)
   
  -**Note:** Out of the box mvn urls are supported, so you can use values like: **mvn:my.groupId/artifactId/1.0.0/json/kubernetes** (work in progress)
  -
  -**Also:** If your project is using maven and dependencies like the above are expressed in the pom, the will be used *automatically*. (work in progress)
  +**Note:** Out of the box mvn urls are supported, so you can use values like: 
  +**mvn:my.groupId/artifactId/1.0.0/json/kubernetes** (work in progress)
  +
  +**Also:** If your project is using maven and dependencies like the above are expressed in the pom, the will be used 
  +*automatically*. (work in progress)
   
   [IMPORTANT]
   ====
   Arquillian Cube Kubernetes needs to authenticate into Kubernetes.
   To do it, Cube reads from `~/.kube/config` user information (token, password).
   
  -For example in case of OpenShift you can use `oc login --username=admin --password=admin` for creating a token for connecting as admin, or `oc config set-credentials myself --username=admin --password=admin` for statically add the username and password and will communicate with Kubernetes to update the `~/.kube/config` file with the info provided.
  +For example in case of OpenShift you can use `oc login --username=admin --password=admin` for creating a token for
  +connecting as admin, or `oc config set-credentials myself --username=admin --password=admin` for statically adding the
  +username and password and communicate with Kubernetes to update the `~/.kube/config` file with the info provided.
   
   You can read more about Kubernetes config file at http://kubernetes.io/docs/user-guide/kubectl/kubectl_config/
   ====
   
   === Readiness and waiting
  -Creating an environment does not guarantee its readiness. For example a Docker image may be required to get pulled by a remote repository and this make take even several minutes.
  -Running a test against a Pod which is not Running state is pretty much pointless, so we need to wait until everything is ready.
  -
  -This extension will wait up to **wait.timeout** until everything is up and running. Everything? It will wait for all Pods and Service *(that were created during the test suite initialization)* to become ready.
  -It will poll them every **wait.poll.interval** milliseconds. For services there is also the option to perform a simple "connection test"  by setting the flag **wait.for.service.connection.enabled** to true.
  -In this case it will not just wait for the service to ready, but also to be usable/connectable.
  +Creating an environment does not guarantee its readiness. For example a Docker image may be required to get pulled by a 
  +remote repository and this make take even several minutes.
  +Running a test against a Pod which is not Running state is pretty much pointless, so we need to wait until everything
  +is ready.
  +
  +This extension will wait up to **wait.timeout** until everything is up and running. Everything? It will wait for all
  +Pods and Service *(that were created during the test suite initialization)* to become ready.
  +It will poll them every **wait.poll.interval** milliseconds. For services there is also the option to perform a simple 
  +"connection test"  by setting the flag **wait.for.service.connection.enabled** to true.
  +In this case it will not just wait for the service to be ready, but also to be usable/connectable.
   
   === Immutable infrastructure and integration testing
   
  
positive.code: 
  === Overview
  
  This extension, wll create and manage a temporary namespace for your tests, apply all Kubernetes resources required to create your environment and once everything is ready it will run your tests. The tests will be enriched with resources required to access services. Finally when testing is over it will cleanup everything.
  
  This extension, will not mutate neither your containers *(by deploying, reconfiguring etc)* nor your Kubernetes resources, and takes a black box approach to testing.
  
  === Modules
  The main modules of this extension are the following:
  
negative.code: to determine the current namespace.
  
  ### Creating the environment
  
  After creating or selecting an existing namespace, the next step is the environment preparation. This is the stage
  where all the required Kubernetes configuration will be applied.
  
  #### How to run kubernetes with multiple configuration files?
  1. Out of the box, the extension will use the classpath and try to find a resource named **kubernetes.json** or 
  **kubernetes.yaml***. The name of the resource can be changed using the **env.config.resource.name**.
  Of course it is also possible to specify an external resource by URL using the **env.config.url**.
  
  2. While finding resource in classpath with property **env.config.resource.name**, cube will look into classpath
  with given name, if not found, then cube will continue to look into classpath under META-INF/fabric8/ directory.
  Using this you can put multiple resources(openshift.json, openshift.yml) inside META-INF/fabric8, and choose only
  required one by specifying **env.config.resource.name** property.
  
  3. Either way, it is possible that the kubernetes configuration used, depends on other configurations. It is also
  possible that your environment configuration is split in multiple files.
  To cover cases like this the **env.dependencies** is provided which accepts a space separated list of URLs.
  
  4. There are cases, where instead of specifying the resources, you want to specify some shell scripts that will setup
  the environment. For those cases you can use the **env.setup.script.url** / **env.teardown.script.url** to pass the
  scripts for setting up and tearing down the environment. Note that these scripts are going to be called right after the
  namespace is created and cleaned up respectively.
  Both scripts will be executed using visible environment variables the following:
  
   * KUBERNETES_MASTER
   * KUBERNETES_NAMESPACE
  