diff --git a/website/source/docs/agent/kv.html.md b/website/source/docs/agent/kv.html.md index 8973209c5a..5ed40fd1e7 100644 --- a/website/source/docs/agent/kv.html.md +++ b/website/source/docs/agent/kv.html.md @@ -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. diff --git a/website/source/docs/agent/options.html.md b/website/source/docs/agent/options.html.md index 53ae2a5f72..c3a360bade 100644 --- a/website/source/docs/agent/options.html.md +++ b/website/source/docs/agent/options.html.md @@ -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. - * `use_cache` - When set to true, DNS resolution will use the agent cache described + * `use_cache` - 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) - * `cache_max_age` - When [use_cache](#dns_use_cache) is enabled, the agent + * `cache_max_age` - 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). * `domain` Equivalent to the diff --git a/website/source/docs/platform/k8s/service-sync.html.md b/website/source/docs/platform/k8s/service-sync.html.md index 66b36da6e5..48fae05196 100644 --- a/website/source/docs/platform/k8s/service-sync.html.md +++ b/website/source/docs/platform/k8s/service-sync.html.md @@ -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.