anchor.diff:  - path - A _mount path_ that must be mounted to the running pod, to load the configmaps or secrets from local disk.
   - kubernetes client - *Autowired* An `io.fabric8.kubernetes.client.KubernetesClient` instance to use for connecting to the Kubernetes API server.
   
  -Camel will autowire the `KubernetesClient` if a single instance of the client exists in the running application (lookup via the xref:registry.adoc[Registry]).
  +Camel will first use _mount paths_ (if configured) to lookup, and then fallback to use the `KubernetesClient`.
  +
  +==== Configuring mount paths for ConfigMaps and Secrets
   
   The configuration of the _month path_ are used by the given order:
   
  -1. Reading configuration property with keys `org.apache.camel.component.kubernetes.properties.mount-path-configmaps`
  -and `org.apache.camel.component.kubernetes.properties.mount-path-secrets`.
  +1. Reading configuration property with keys `camel.kubernetes.mount-path-configmaps`
  +and `camel.kubernetes.mount-path-secrets`.
   2. Use JVM system property with key `camel.k.mount-path.configmaps` and `camel.k.mount-path.secrets` (Camel K compatible).
   3. Use OS ENV variable with key `camel.k.mount-path.configmaps` and `camel.k.mount-path.secrets` (Camel K compatible).
   
  
positive.code: 
  [source,properties]
  ----
  org.apache.camel.component.kubernetes.properties.mount-path-configmaps = /etc/camel/myconfig/
  org.apache.camel.component.kubernetes.properties.mount-path-secrets = /etc/camel/mysecrets/
  ----
  
  ==== Using configmap with Kubernetes
  
  
negative.code: configmap:name/key[:defaultValue]
  ----
  
  Where the default value is optional, for example the following will lookup `myKey`,
  and fail if there is no such configmap.
  
  [source]
  ----
  configmap:mymap/mykey
  ----
  
  In this example then it would not fail as a default value is provided:
  
  [source]
  ----
  configmap:mymap/mykey:123
  ----
  
  