anchor.diff:  === 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** to false and keep the namespace around.
  +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
  
positive.code: **Note:** When checking for environment variables, property names will get capitalized, and symbols like "." will be converted to "_".
  For example **foo.bar.baz** will be converted to **FOO_BAR_BAZ**.
  
  ==== Kubernetes
  
  [width="80%"]
  |===============================================================================================================================================
  
negative.code: 
  2. 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.
  
  3. There are cases, where instead of specifying the resources, you want to specify some shell scripts that will setup the environment. For those case 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.
  
  (You can use any custom URL provided the appropriate URL stream handler.)
  
  