anchor.diff:      }
   ----
   
  -The test code above, demonstrates how you can inject an use inside your test the *KubernetesClient* and the *Session* object. It also demonstrates the use of **kubernetes-assertions** which is a nice little library based on [assert4j](http://assertj.org) for performing assertions on top of the Kubernetes model.
  +The test code above, demonstrates how you can inject an use inside your test the *KubernetesClient* and the
  +*Session* object.
  +It also demonstrates the use of **kubernetes-assertions** which is a nice little library based on 
  +http://assertj.org[assert4j] for performing assertions on top of the Kubernetes model.
   
   The next example is intended to how you can inject a resource by id.
   
  
positive.code: 
  === Namespaces
  
  The default behavior of the extension is to create a unique namespace per test suite. The namespace is created Before the suite is started and destroyed in the end.
  For debugging purposes, you can set the **namespace.cleanup.enabled** and **namespace.destroy.enabled**  to false and keep the namespace around.
  
  In other cases you may find it useful to manually create and manage the environment rather than having **arquillian** do that for you.
  In this case you can use the **namespace.use.existing** option to select an existing namespace. This option goes hand in hand with **env.init.enabled** which can be
  used to prevent the extension from modifying the environment.
  
  Last but not least, you can just tell arquillian, that you are going to use the current namespace. In this case, arquillian cube will delegate to the link:https://github.com/fabric8io/kubernetes-client/[Kubernetes Client] that will use:
  
  - ~/.kube/config
  - /var/run/secrets/kubernetes.io/serviceaccount/namespace
  
negative.code: 
  === Overview
  
  This extension will 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 neither mutate 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:
  