mirror of
https://github.com/status-im/consul.git
synced 2025-02-22 10:28:31 +00:00
website: fix broken links
This commit is contained in:
parent
feaece034b
commit
a99f7aaa25
@ -14,7 +14,7 @@ The Consul KV datastore is located on the servers, but can be accessed by any ag
|
||||
|
||||
## Accessing the KV store
|
||||
|
||||
The KV store can be accessed by the [consul kv CLI subcommands](/docs/commands/kv.html), [HTTP API](/api/kv.html), and Consul UI. To restrict access, enable and configure [ACLs](https://learn.hashicorp.com/consul/advanced/day-1-operations/acl-guide). Once the ACL system has been bootstrapped, users and services, will need a valid token with KV [privileges](docs/agent/acl-rules.html#key-value-rules) to access the the data store, this includes even reads. We recommend creating a token with limited privileges, for example, you could create a token with write privileges on one key for developers to update the value related to their application.
|
||||
The KV store can be accessed by the [consul kv CLI subcommands](/docs/commands/kv.html), [HTTP API](/api/kv.html), and Consul UI. To restrict access, enable and configure [ACLs](https://learn.hashicorp.com/consul/advanced/day-1-operations/acl-guide). Once the ACL system has been bootstrapped, users and services, will need a valid token with KV [privileges](/docs/agent/acl-rules.html#key-value-rules) to access the the data store, this includes even reads. We recommend creating a token with limited privileges, for example, you could create a token with write privileges on one key for developers to update the value related to their application.
|
||||
|
||||
The datastore itself is located on the Consul servers in the [data directory](/docs/agent/options.html#_data_dir). To ensure data is not lost in the event of a complete outage, use the [`consul snapshot`](/docs/commands/snapshot/restore.html) feature to backup the data.
|
||||
|
||||
|
@ -1075,10 +1075,10 @@ default will automatically work with some tooling.
|
||||
Configures the Retry duration expressed in seconds, default value is
|
||||
600, ie: 10 minutes.
|
||||
|
||||
* <a name="dns_use_cache"></a><a href="dns_use_cache">`use_cache`</a> - When set to true, DNS resolution will use the agent cache described
|
||||
* <a name="dns_use_cache"></a><a href="#dns_use_cache">`use_cache`</a> - When set to true, DNS resolution will use the agent cache described
|
||||
in [agent caching](/api/index.html#agent-caching). This setting affects all service and prepared queries DNS requests. Implies [`allow_stale`](#allow_stale)
|
||||
|
||||
* <a name="dns_cache_max_age"></a><a href="dns_cache_max_age">`cache_max_age`</a> - When [use_cache](#dns_use_cache) is enabled, the agent
|
||||
* <a name="dns_cache_max_age"></a><a href="#dns_cache_max_age">`cache_max_age`</a> - When [use_cache](#dns_use_cache) is enabled, the agent
|
||||
will attempt to re-fetch the result from the servers if the cached value is older than this duration. See: [agent caching](/api/index.html#agent-caching).
|
||||
|
||||
* <a name="domain"></a><a href="#domain">`domain`</a> Equivalent to the
|
||||
|
@ -76,7 +76,7 @@ For Consul, if ACLs are configured on the cluster, a Consul
|
||||
[ACL token](https://learn.hashicorp.com/consul/advanced/day-1-operations/acl-guide)
|
||||
will need to be provided. Review the [ACL rules](/docs/agent/acl-rules.html)
|
||||
when creating this token so that it only allows the necessary privileges. The catalog
|
||||
sync process accepts this token by using the [`CONSUL_HTTP_TOKEN`](docs/commands/index.html#consul_http_token)
|
||||
sync process accepts this token by using the [`CONSUL_HTTP_TOKEN`](/docs/commands/index.html#consul_http_token)
|
||||
environment variable. This token should be set as a
|
||||
[Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/secret/#creating-your-own-secrets)
|
||||
and referenced in the Helm chart.
|
||||
|
Loading…
x
Reference in New Issue
Block a user