anchor.diff:           # Spring Cloud Kubernetes will lookup a ConfigMap named c3 in namespace n3
            - namespace: n3
              name: c3
  +```
   
   In the example above, it `spring.cloud.kubernetes.config.namespace` had not been set,
   then the ConfigMap named `c1` would be looked up in the namespace that the application runs
  
positive.code: | spring.cloud.kubernetes.reload.monitoring-secrets      | Boolean | false                      | Allow monitoring changes in secrets
  | spring.cloud.kubernetes.reload.strategy                | Enum    | refresh                    | The strategy to use when firing a reload (*refresh*, *restart_context*, *shutdown*)
  | spring.cloud.kubernetes.reload.mode                    | Enum    | event                      | Specifies how to listen for changes in property sources (*event*, *polling*)
  | spring.cloud.kubernetes.reload.period                  | Long    | 15000                      | The period in milliseconds for verifying changes when using the *polling* strategy
  |===
  **Notes**:
  - Properties under *spring.cloud.kubernetes.reload.* should not be used in config maps or secrets: changing such properties at runtime may lead to unexpected results;
  - Deleting a property or the whole config map does not restore the original state of the beans when using the *refresh* level.
  
  
  # Ribbon discovery in Kubernetes
  
  
  Spring Cloud client applications calling a microservice should be interested on relying on a client load-balancing
  
negative.code: data:
    application.properties: |-
      bean.message=Hello World!
  ```
  
  Any change to the property named `bean.message` in the `ConfigMap` associated to the pod will be reflected in the
  output. More generally speaking, changes associated to properties prefixed with the value defined by the `prefix`
  