Bumping versions
This commit is contained in:
@@ -1195,6 +1195,7 @@ field of the `@ConfigurationProperties` annotation are detected and reflected in
|
||||
The full example is available in https://github.com/spring-cloud/spring-cloud-kubernetes/tree/main/spring-cloud-kubernetes-examples/kubernetes-reload-example[`spring-cloud-kubernetes-reload-example`].
|
||||
|
||||
The reload feature supports two operating modes:
|
||||
|
||||
* Event (default): Watches for changes in config maps or secrets by using the Kubernetes API (web socket).
|
||||
Any event produces a re-check on the configuration and, in case of changes, a reload.
|
||||
The `view` role on the service account is required in order to listen for config map changes. A higher level role (such as `edit`) is required for secrets
|
||||
@@ -1270,6 +1271,7 @@ What this will do, is watch configmaps/secrets that only have the `spring.cloud.
|
||||
|===
|
||||
|
||||
Notes:
|
||||
|
||||
* You should not use properties under `spring.cloud.kubernetes.reload` 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 you use the `refresh` level.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user