anchor.diff:      SpringApplication.run(Application.class, args);
     }
   }
  +```
   
   Then you can inject the client in your code simply by:
   
  -[source,java]
  +```java
   @Autowired
   private DiscoveryClient discoveryClient;
  +```
   
   If for any reason you need to disable the `DiscoveryClient` you can simply set the following property in `application.properties`:
   
  -----
  +```
   spring.cloud.kubernetes.discovery.enabled=false
  -----
  +```
   
   Some Spring Cloud components use the `DiscoveryClient` in order to obtain info about the local service instance. For
   this to work you need to align the Kubernetes service name with the `spring.application.name` property.
   
  -= Kubernetes PropertySource implementations
  +== Kubernetes native service discovery
  +
  +Kubernetes itself is capable of (server side) service discovery (see: https://kubernetes.io/docs/concepts/services-networking/service/#discovering-services).
  +Using native kubernetes service discovery ensures compatibility with additional tooling, like: istio https://istio.io (service mesh, capable of load balancing, ribbon, circuit breaker, failover and much more).
  +
  +The caller service just needs to refer to names resolvable in particular kubernetes cluster then. Simplest implementation might use the spring `RestTemplate` referring to fully qualified domain name (FQDN) `http://{service-name}.{namespace}.svc.{cluster}.local:{service-port}`.
  +
  +Additionally, hystrix can be used for:
  +
  +* circuit breaker implementation on the caller side, just by annotating the spring boot application class: `@EnableCircuitBreaker`
  +* and for the fallback functionality, annotating the respective method via: `@HystrixCommand(fallbackMethod=` does the job.
  +
  +== Kubernetes PropertySource implementations
   
   The most common approach to configure your Spring Boot application is to create an `application.properties|yaml` or
   an `application-profile.properties|yaml` file containing key-value pairs providing customization values to your
   application or Spring Boot starters. Users may override these properties by specifying system properties or environment
   variables.
   
  -== ConfigMap PropertySource
  +=== ConfigMap PropertySource
   
   Kubernetes provides a resource named http://kubernetes.io/docs/user-guide/configmap/[ConfigMap] to externalize the
   parameters to pass to your application in the form of key-value pairs or embedded `application.properties|yaml` files.
  
positive.code:             fieldPath: "metadata.namespace"
  
  
  ## Service Account
  For distros of Kubernetes that support more fine-grained role-based access within the cluster, you need to make sure a pod that runs with spring-cloud-kubernetes has access to the Kubernetes API.
  For any service accounts you assign to a deployment/pod, you need to make sure it has the correct roles. For example, you can add `cluster-reader` permissions to your `default` service account depending on the project you're in:
  
  = Examples
  
  List of examples using these projects:
  
  <TBD>
  
  = Other Resources
  
  == Building
  
  
negative.code:       size:
          core: 1
          max:16
  ```
  
  The following also works:
  
   ```yaml
  kind: ConfigMap
  apiVersion: v1
  metadata:
  