Fix cross references

This commit is contained in:
spencergibb
2023-09-19 13:10:00 -04:00
parent 69f0bbb9b9
commit 7c5f582490
6 changed files with 11 additions and 11 deletions

View File

@@ -23,7 +23,7 @@ HTTP Based `DiscoveryClient`
====
NOTE: `spring-cloud-starter-kubernetes-discoveryclient` is designed to be used with the
<<spring-cloud-kubernetes-discoveryserver, Spring Cloud Kubernetes DiscoveryServer>>.
xref:spring-cloud-kubernetes-discoveryserver.adoc#spring-cloud-kubernetes-discoveryserver[Spring Cloud Kubernetes DiscoveryServer].
====
Fabric8 Kubernetes Client
@@ -156,7 +156,7 @@ spring:
- namespace-b
```
- we will use: xref:property-source-config.adoc#namespace-resolution[Namespace Resolution] if the above two paths are not taken.
- we will use: xref:property-source-config/namespace-resolution.adoc[Namespace Resolution] if the above two paths are not taken.
In order to enable this functionality you need to add
`@EnableScheduling` on a configuration class in your application.

View File

@@ -50,8 +50,8 @@ resolves service names to Kubernetes Services.
</dependency>
----
| Load application properties from Kubernetes
<<configmap-propertysource,ConfigMaps>> and <<Secrets PropertySource,Secrets>>.
<<propertysource-reload,Reload>> application properties when a ConfigMap or
xref:property-source-config/configmap-propertysource.adoc[ConfigMaps] and <<Secrets PropertySource,Secrets>>.
xref:property-source-config/propertysource-reload.adoc[Reload] application properties when a ConfigMap or
Secret changes.
| [source,xml]

View File

@@ -42,7 +42,7 @@ spring:
In the preceding example, if `spring.cloud.kubernetes.config.namespace` had not been set,
the `ConfigMap` named `c1` would be looked up in the namespace that the application runs.
See <<namespace-resolution,Namespace resolution>> to get a better understanding of how the namespace
See xref:property-source-config/namespace-resolution.adoc[Namespace resolution] to get a better understanding of how the namespace
of the application is resolved.

View File

@@ -1,7 +1,7 @@
[[namespace-label-filtering]]
= Reload namespace and label filtering
By default, a namespace chosen using the steps outlined in <<namespace-resolution,Namespace resolution>> will be used to listen to changes
By default, a namespace chosen using the steps outlined in xref:property-source-config/namespace-resolution.adoc[Namespace resolution] will be used to listen to changes
in configmaps and secrets. i.e.: if you do not tell reload what namespaces and configmaps/secrets to watch for,
it will watch all configmaps/secrets from the namespace that will be computed using the above algorithm.

View File

@@ -2,7 +2,7 @@
= `PropertySource` Reload
WARNING: This functionality has been deprecated in the 2020.0 release. Please see
the <<spring-cloud-kubernetes-configuration-watcher>> controller for an alternative way
the xref:spring-cloud-kubernetes-configuration-watcher.adoc#spring-cloud-kubernetes-configuration-watcher[null] controller for an alternative way
to achieve the same functionality.
Some applications may need to detect changes on external property sources and update their internal status to reflect the new configuration.
@@ -92,7 +92,7 @@ data:
Any change to the property named `bean.message` in the `ConfigMap` associated with the pod is reflected in the
output. More generally speaking, changes associated to properties prefixed with the value defined by the `prefix`
field of the `@ConfigurationProperties` annotation are detected and reflected in the application.
<<configmap-propertysource,Associating a `ConfigMap` with a pod>> is explained earlier in this chapter.
xref:property-source-config/configmap-propertysource.adoc[Associating a `ConfigMap` with a pod] is explained earlier in this chapter.
The reload feature supports two operating modes:

View File

@@ -148,13 +148,13 @@ spring:
In the preceding example, if `spring.cloud.kubernetes.secrets.namespace` had not been set,
the `Secret` named `s1` would be looked up in the namespace that the application runs.
See <<namespace-resolution,namespace-resolution>> to get a better understanding of how the namespace
See xref:property-source-config/namespace-resolution.adoc[namespace-resolution] to get a better understanding of how the namespace
of the application is resolved.
<<config-map-fail-fast,Similar to the `ConfigMaps`>>; if you want your application to fail to start
xref:property-source-config/configmap-propertysource.adoc#config-map-fail-fast[Similar to the `ConfigMaps`]; if you want your application to fail to start
when it is unable to load `Secrets` property sources, you can set `spring.cloud.kubernetes.secrets.fail-fast=true`.
It is also possible to enable retry for `Secret` property sources <<config-map-retry,like the `ConfigMaps`>>.
It is also possible to enable retry for `Secret` property sources xref:property-source-config/configmap-propertysource.adoc#config-map-retry[like the `ConfigMaps`].
As with the `ConfigMap` property sources, first you need to set `spring.cloud.kubernetes.secrets.fail-fast=true`.
Then you need to add `spring-retry` and `spring-boot-starter-aop` to your classpath.
Retry behavior of the `Secret` property sources can be configured by setting the `spring.cloud.kubernetes.secrets.retry.*`