diff --git a/website/content/docs/k8s/annotations-and-labels.mdx b/website/content/docs/k8s/annotations-and-labels.mdx index 204e4fcfa0..dc95b8f216 100644 --- a/website/content/docs/k8s/annotations-and-labels.mdx +++ b/website/content/docs/k8s/annotations-and-labels.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Annotations and Labels description: >- -Annotations and labels configure Consul sidecar properties and injection behavior when scheduling Kubernetes clusters. Learn about the required annotations and labels that enable Consul’s service mesh and secure upstream communication on k8s in this reference guide. +Annotations and labels configure Consul sidecar properties and injection behavior when scheduling Kubernetes clusters. Learn about the annotations and labels that enable Consul’s service mesh and secure upstream communication on k8s in this reference guide. --- # Annotations and Labels diff --git a/website/content/docs/k8s/connect/observability/metrics.mdx b/website/content/docs/k8s/connect/observability/metrics.mdx index 5d822396cc..91e9510921 100644 --- a/website/content/docs/k8s/connect/observability/metrics.mdx +++ b/website/content/docs/k8s/connect/observability/metrics.mdx @@ -5,7 +5,7 @@ description: >- Use the `connectInject.metrics` Helm values to enable Prometheus and Grafana integrations and capture metrics. Consul can collect metrics from the service mesh, sidecar proxies, agents, and gateways in a k8s cluster and then display service traffic metrics in Consul’s UI for additional observability. --- -# Configure metrics for Consul on Kubernetes +# Configure Metrics for Consul on Kubernetes Consul on Kubernetes integrates with Prometheus and Grafana to provide metrics for Consul Service Mesh. The metrics available are: diff --git a/website/content/docs/k8s/crds/upgrade-to-crds.mdx b/website/content/docs/k8s/crds/upgrade-to-crds.mdx index bcbe491f0f..4dc5ab7325 100644 --- a/website/content/docs/k8s/crds/upgrade-to-crds.mdx +++ b/website/content/docs/k8s/crds/upgrade-to-crds.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Upgrade Existing Clusters to Use Custom Resource Definitions description: >- -Kubernetes clusters configured with a Consul Helm chart version older than 0.30.0 require updates in order to use CRDs. Learn about the changes you need to make, as well as how to migrate a Consul config entry to a k8s CRD. +Kubernetes clusters configured with a Consul Helm chart version older than 0.30.0 require updates in order to use CRDs. Learn about upgrading to a supported Helm version and how to migrate a Consul config entry to a k8s CRD. --- # Upgrade Existing Clusters to Use Custom Resource Definitions diff --git a/website/content/docs/k8s/dns.mdx b/website/content/docs/k8s/dns.mdx index 73abb6a9ef..6db0f664e8 100644 --- a/website/content/docs/k8s/dns.mdx +++ b/website/content/docs/k8s/dns.mdx @@ -5,7 +5,7 @@ description: >- Use a k8s ConfigMap to configure KubeDNS or CoreDNS so that you can use Consul's `.service.consul` syntax for queries and other DNS requests. In Kubernetes, this process uses either stub-domain or proxy configuration. --- -# Resolve Consul DNS requests in Kubernetes +# Resolve Consul DNS Requests in Kubernetes One of the primary query interfaces to Consul is the [DNS interface](/docs/discovery/dns). You can configure Consul DNS in diff --git a/website/content/docs/k8s/index.mdx b/website/content/docs/k8s/index.mdx index ffdc3f2664..9f24a98ab7 100644 --- a/website/content/docs/k8s/index.mdx +++ b/website/content/docs/k8s/index.mdx @@ -1,11 +1,11 @@ --- layout: docs -page_title: Consul & Kubernetes +page_title: Consul on Kubernetes description: >- Consul supports Kubernetes natively, allowing you to deploy Consul sidecars to a Kubernetes service mesh and sync the k8s service registry with non-k8s services. Learn how to install Consul on Kubernetes with Helm or the Consul K8s CLI and get started with tutorials. --- -# Consul & Kubernetes +# Consul on Kubernetes Consul has many integrations with Kubernetes. You can deploy Consul to Kubernetes using the [Helm chart](/docs/k8s/installation/install#helm-chart-installation) or [Consul K8s CLI](/docs/k8s/installation/install#consul-k8s-cli-installation), sync services between Consul and diff --git a/website/content/docs/k8s/operations/certificate-rotation.mdx b/website/content/docs/k8s/operations/certificate-rotation.mdx index 69ff7d53f5..a7337abb65 100644 --- a/website/content/docs/k8s/operations/certificate-rotation.mdx +++ b/website/content/docs/k8s/operations/certificate-rotation.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Rotate TLS Certificates for Consul on Kubernetes description: >- -As of Consul Helm version 0.29.0, new server agent TLS certificates are issued every time the Helm version is upgraded. Learn how to trigger certificate rotation manually when it doesn't happen automatically. +In Consul Helm version 0.29.0 and later, new server agent TLS certificates are issued every time the Helm version is upgraded. Learn how to manually trigger certificate rotation if they do not rotate automatically. --- # Rotate TLS Certificates for Consul on Kubernetes diff --git a/website/content/docs/k8s/operations/tls-on-existing-cluster.mdx b/website/content/docs/k8s/operations/tls-on-existing-cluster.mdx index 82498eea7c..07ffa89ddc 100644 --- a/website/content/docs/k8s/operations/tls-on-existing-cluster.mdx +++ b/website/content/docs/k8s/operations/tls-on-existing-cluster.mdx @@ -2,7 +2,7 @@ layout: docs page_title: Rolling Updates to TLS for Existing Clusters on Kubernetes description: >- -Consul's Helm chart began supporting TLS communication within clusters in version 0.16.0. Follow the instructions to trigger rolling updates for consul-k8s without causing downtime. +Consul Helm chart 0.16.0 and later supports TLS communication within clusters. Follow the instructions to trigger rolling updates for consul-k8s without causing downtime. --- # Rolling Updates to TLS for Existing Clusters on Kubernetes