/docs/k8s

This commit is contained in:
boruszak 2022-09-14 17:26:14 -05:00
parent 8100a5b67f
commit 62eda6c9eb
8 changed files with 22 additions and 27 deletions

View File

@ -2,7 +2,7 @@
layout: docs
page_title: Annotations and Labels
description: >-
The list of available labels and annotations for running Consul on Kubernetes.
Annotations and labels configure Consul sidecar properties and injection behavior when scheduling Kubernetes clusters. Learn about the required annotations and labels that enable Consuls service mesh and secure upstream communication on k8s in this reference guide.
---
# Annotations and Labels

View File

@ -1,8 +1,8 @@
---
layout: docs
page_title: Consul on Kubernetes Architecture
page_title: Consul on Kubernetes Control Plane Architecture
description: >-
A high level overview of Consul on Kubernetes Architecture
When running on Kubernetes, Consuls control plane architecture does not change significantly. Server agents are deployed as a StatefulSet with a persistent volume, while client agents run as a k8s DaemonSet with an exposed API port.
---

View File

@ -1,10 +1,11 @@
---
layout: docs
page_title: Compatibility Matrix
description: Compatibility Matrix for Consul Kubernetes
page_title: Consul on Kubernetes Version Compatibility
description: >-
New releases require corresponding version updates to Consul on Kubernetes and its Helm chart. Review the compatibility matrix for Consul and consul-k8s and additional notes for integrating Vault and third-party platforms.
---
# Compatibility Matrix for Consul on Kubernetes
# Consul on Kubernetes Version Compatibility
For every release of Consul on Kubernetes, a Helm chart, `consul-k8s-control-plane` binary and a `consul-k8s` CLI binary is built and distributed through a single version. When deploying via Helm, the recommended best path for upgrading Consul on Kubernetes, is to upgrade using the same `consul-k8s-control-plane` version as the Helm Chart, as the Helm Chart and Control Plane binary are tightly coupled.

View File

@ -1,13 +1,11 @@
---
layout: docs
page_title: Consul DNS - Kubernetes
page_title: Resolve Consul DNS requests in Kubernetes
description: >-
One of the primary query interfaces to Consul is the DNS interface. The Consul
DNS interface can be exposed for all pods in Kubernetes using a stub-domain
configuration.
Use a k8s ConfigMap to configure KubeDNS or CoreDNS so that you can use Consul's `<service-name>.service.consul` syntax for queries and other DNS requests. In Kubernetes, this process uses either stub-domain or proxy configuration.
---
# Consul DNS on 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

View File

@ -1,10 +1,11 @@
---
layout: docs
page_title: Helm Chart Configuration
description: Configuration for the Consul Helm chart.
page_title: Helm Chart Reference
description: >-
The Helm Chart allows you to schedule Kubernetes clusters with injected Consul sidecars by defining custom values in a YAML configuration. Find stanza hierarchy, the parameters you can set, and their default values in this k8s reference guide.
---
# Helm Chart Configuration
# Helm Chart Reference
The chart is highly customizable using
[Helm configuration values](https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing).

View File

@ -1,14 +1,11 @@
---
layout: docs
page_title: Kubernetes
page_title: Consul & Kubernetes
description: >-
Consul has many integrations with Kubernetes. You can deploy Consul to
Kubernetes using the Helm chart, sync services between Consul and Kubernetes,
automatically secure Pod communication with Connect, and more. This section
documents the official integrations between Consul and Kubernetes.
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.
---
# Kubernetes
# Consul & 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

View File

@ -1,8 +1,8 @@
---
layout: docs
page_title: Consul K8s CLI Reference
page_title: Consul on Kubernetes CLI Reference
description: >-
The Consul on Kubernetes CLI (consul-k8s) is a tool for installing and managing Consul on Kubernetes.
The Consul on Kubernetes CLI tool enables you to manage Consul with the `consul-k8s` command instead of direct interaction with Helm, kubectl, or Consuls CLI. Learn about commands, their flags, and review examples in this reference guide.
---
# Consul on Kubernetes CLI Reference

View File

@ -1,13 +1,11 @@
---
layout: docs
page_title: Service Sync - Kubernetes
page_title: Service Sync for Consul on Kubernetes
description: >-
The services in Kubernetes and Consul can be automatically synced so that
Kubernetes services are available to Consul agents and services in Consul can
be available as first-class Kubernetes services.
Service sync is a Consul on Kubernetes feature that makes Kubernetes and Consul services available to each other. Learn how to configure Helm values so services can communicate and make Kubernetes services appear in the Consul UI.
---
# Syncing Kubernetes and Consul Services
# Service Sync for Consul on Kubernetes
The services in Kubernetes and Consul can be automatically synced so that Kubernetes
services are available to Consul agents and services in Consul can be available