Refactor Config Module And Add A New Config Module Using Kubernetes Client (#664)

* Deprecate KubernetesAutoServiceRegistration

* Document service registry in kubernetes.  Fixes #348

* Refactoring config module to extract common code
Renamed config module to be specific to fabric8

* Kubernetes client config module

* Fixing test to avoid 503 error

* Accounting for missing invocation

* Adding code to deal with potential 503 error

* Fixing class used in polling change listener

* Formatting changes
This commit is contained in:
Ryan Baxter
2020-11-24 20:25:20 -05:00
committed by GitHub
parent d2704f0174
commit a47a530bc3
137 changed files with 3691 additions and 617 deletions

View File

@@ -14,7 +14,7 @@ The link:./spring-cloud-kubernetes-config[Spring Cloud Kubernetes Config] projec
during application bootstrapping and triggers hot reloading of beans or Spring context when changes are detected on
observed `ConfigMap` instances.
The default behavior is to create a `ConfigMapPropertySource` based on a Kubernetes `ConfigMap` that has a `metadata.name` value of either the name of
The default behavior is to create a `Fabric8ConfigMapPropertySource` based on a Kubernetes `ConfigMap` that has a `metadata.name` value of either the name of
your Spring application (as defined by its `spring.application.name` property) or a custom name defined within the
`bootstrap.properties` file under the following key: `spring.cloud.kubernetes.config.name`.
@@ -300,7 +300,7 @@ Kubernetes has the notion of https://kubernetes.io/docs/concepts/configuration/s
sensitive data such as passwords, OAuth tokens, and so on. This project provides integration with `Secrets` to make secrets
accessible by Spring Boot applications. You can explicitly enable or disable This feature by setting the `spring.cloud.kubernetes.secrets.enabled` property.
When enabled, the `SecretsPropertySource` looks up Kubernetes for `Secrets` from the following sources:
When enabled, the `Fabric8SecretsPropertySource` looks up Kubernetes for `Secrets` from the following sources:
. Reading recursively from secrets mounts
. Named after the application (as defined by `spring.application.name`)