anchor.diff:  
   The implementation is part of the following starter that you can use by adding its dependency to your pom file:
   
  -```xml
  +[source,xml]
   <dependency>
       <groupId>org.springframework.cloud</groupId>
       <artifactId>spring-cloud-starter-kubernetes-netflix</artifactId>
       <version>${latest.version}</version>
   </dependency>
  -```
   
   When the list of the endpoints is populated, the Kubernetes client will search the registered endpoints living in
   the current namespace/project matching the service name defined using the Ribbon Client annotation:
   
  -```java
  +[source,java]
   @RibbonClient(name = "name-service")
  -```
   
   You can configure Ribbon's behavior by providing properties in your `application.properties` (via your application's
   dedicated `ConfigMap`) using the following format: `<name of your service>.ribbon.<Ribbon configuration key>` where:
  
positive.code: ## Namespace
  Most of the components provided in this project need to know the namespace. For Kubernetes (1.3+) the namespace is made available to pod as part of the service account secret and automatically detected by the client.
  For earlier version it needs to be specified as an env var to the pod. A quick way to do this is:
  
        env:
        - name: "KUBERNETES_NAMESPACE"
          valueFrom:
  
negative.code:   selfLink: /api/v1/namespaces/default/secrets/db-secret
    uid: 63c89263-6099-11e7-b3da-76d6186905a8
  type: Opaque
  
  Note that the data contains Base64-encoded versions of the literal provided by the create command.
  
  This secret can then be used by your application for example by exporting the secret's value as environment variables:
  
  [source,yaml]
  apiVersion: v1
  kind: Deployment
  metadata:
  