mirror of https://github.com/status-im/consul.git
Improve doc: add note about address validation (#10123)
* Update website/content/docs/discovery/services.mdx with address field behavior. Co-authored-by: Jono Sosulska <42216911+jsosulska@users.noreply.github.com> Co-authored-by: Jono Sosulska <42216911+jsosulska@users.noreply.github.com>
This commit is contained in:
parent
8dffb89131
commit
5220699696
|
@ -120,8 +120,9 @@ different versions, or any other service level labels.
|
||||||
We recommend using [valid DNS labels](https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_hostnames)
|
We recommend using [valid DNS labels](https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_hostnames)
|
||||||
for service definition names and tags for [compatibility with external DNS](/docs/agent/services#service-and-tag-names-with-dns)
|
for service definition names and tags for [compatibility with external DNS](/docs/agent/services#service-and-tag-names-with-dns)
|
||||||
|
|
||||||
The `address` field can be used to specify a service-specific IP address. By
|
The `address` field is optional, and can be used to specify a service-specific IP address or a hostname.
|
||||||
default, the IP address of the agent is used, and this does not need to be provided.
|
There is no server-side validation of this field, and it can be set to any string. When this value is not provided,
|
||||||
|
the IP address of the agent node is used by default.
|
||||||
The `port` field can be used as well to make a service-oriented architecture
|
The `port` field can be used as well to make a service-oriented architecture
|
||||||
simpler to configure; this way, the address and port of a service can
|
simpler to configure; this way, the address and port of a service can
|
||||||
be discovered.
|
be discovered.
|
||||||
|
|
Loading…
Reference in New Issue