doc

Signed-off-by: wind57 <[email protected]>

Author: wind57

docs/modules/ROOT/pages/property-source-config/configmap-propertysource.adoc

@@ -588,6 +588,9 @@ NOTE: If you already have `spring-retry` and `spring-boot-starter-aspectj` on th
 and want to enable fail-fast, but do not want retry to be enabled; you can disable retry for `ConfigMap` `PropertySources`
 by setting `spring.cloud.kubernetes.config.retry.enabled=false`.
 
+
+NOTE: Since version `5.0.0-M3`, we have introduced the possibility to read sources individually. Until now, we would go to the namespace and read all the configmaps / secrets available and then filter out the ones requested. Since, `5.0.0-M3` you can specify that you want to read them individually, by setting the property: `spring.cloud.kubernetes.config.read-type=SINGLE`. The previous option to read them all in a namespace is controlled by `spring.cloud.kubernetes.config.read-type=BATCH` and it is the default option.
+
 .Properties:
 [options="header,footer"]
 |===

docs/modules/ROOT/pages/spring-cloud-kubernetes-configserver.adoc

@@ -11,37 +11,39 @@ A default image is located on https://hub.docker.com/r/springcloud/spring-cloud-
 the code and image yourself.  However, if you need to customize the config server behavior or prefer to build the image yourself you can easily build your own
 image from the https://github.com/spring-cloud/spring-cloud-kubernetes/tree/main/spring-cloud-kubernetes-controllers/spring-cloud-kubernetes-configserver[source code on GitHub] and use that.
 
-## Configuration
+== Configuration
 
-### Enabling The Kubernetes Environment Repository
+=== Enabling The Kubernetes Environment Repository
 To enable the Kubernetes environment repository the `kubernetes` profile must be included in the list of active profiles.
 You may activate other profiles as well to use other environment repository implementations.
 
-### Config Map and Secret PropertySources
+=== Config Map and Secret PropertySources
 By default, only Config Map data will be fetched.  To enable Secrets as well you will need to set `spring.cloud.kubernetes.secrets.enableApi=true`.
 You can disable the Config Map `PropertySource` by setting `spring.cloud.kubernetes.config.enableApi=false`.
 
-### Fetching Config Map and Secret Data From Additional Namespaces
+=== Fetching Config Map and Secret Data From Additional Namespaces
 By default, the Kubernetes environment repository will only fetch Config Map and Secrets from the namespace in which it is deployed.
 If you want to include data from other namespaces you can set `spring.cloud.kubernetes.configserver.config-map-namespaces` and/or `spring.cloud.kubernetes.configserver.secrets-namespaces` to a comma separated
 list of namespace values.
 
 NOTE: If you set `spring.cloud.kubernetes.configserver.config-map-namespaces` and/or `spring.cloud.kubernetes.configserver.secrets-namespaces`
 you will need to include the namespace in which the Config Server is deployed in order to continue to fetch Config Map and Secret data from that namespace.
 
-### Using Advanced Features Of Spring Vault
+=== Using Advanced Features Of Spring Vault
 In order to use some of the https://docs.spring.io/spring-cloud-config/reference/server/environment-repository/vault-backend.html[more advanced Spring Vault features] of the **Spring Cloud Config Server**, https://mvnrepository.com/artifact/org.springframework.vault/spring-vault-core[`spring-vault-core`] must be on the classpath. By default, Spring Cloud Kubernetes can generate a Docker image for deploying Config Server to Kubernetes, but it does not include `spring-vault-core` in the classpath. If you need `spring-vault-core` to enable certain functionality in the Config Server you can build your own version of Docker image by enabling the `vault` Maven profile when running Maven build.
 
 Example:
-```bash
+
+[source,bash]
+----
 $ ../../mvnw clean install -Pvault
-```
+----
 
-### Kubernetes Access Controls
+=== Kubernetes Access Controls
 The Kubernetes Config Server uses the Kubernetes API server to fetch Config Map and Secret data.  In order for it to do that
 it needs ability to `get` and `list` Config Map and Secrets (depending on what you enable/disable).
 
-## Deployment Yaml
+== Deployment Yaml
 
 Below is a sample deployment, service and permissions configuration you can use to deploy a basic Config Server to Kubernetes.