/docs/k8s/connect
This commit is contained in:
boruszak
parent
0996dab76b
commit
bf807c2c07
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
"---
|
||||
layout: docs
|
||||
page_title: Configuring a Connect CA Provider
|
||||
description: Configuring a Connect CA Provider
|
||||
---
|
||||
page_title: Configure Certificate Authority (CA) for Consul on Kubernetes
|
||||
description: >-
|
||||
Consul includes a built-in CA, but when bootstrapping a cluster on k8s, you can configure your service mesh to use a custom certificate provider instead. Learn how to configure Vault as an external CA in primary and secondary datacenters and manually rotate Vault tokens.
|
||||
---"
|
||||
|
||||
# Configuring a Connect CA Provider
|
||||
# Configure Certificate Authority (CA) for Consul on Kubernetes
|
||||
|
||||
~> **NOTE:** The instructions below should only be used for initially bootstrapping a cluster with **Consul K8s 0.38.0+.**
|
||||
To update the Connect CA provider on an existing cluster or to update any properties, such as tokens, of the CA provider,
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Kubernetes Health Checks
|
||||
description: Configuring Kubernetes Health Checks
|
||||
page_title: Configure Health Checks for Consul on Kubernetes
|
||||
description: >-
|
||||
Kubernetes has built-in health probes you can sync with Consul's health checks to ensure service mesh traffic is routed to healthy pods. Learn how to register a TTL Health check and use mutating webhooks to redirect k8s liveness, readiness, and startup probes through Envoy proxies.
|
||||
---
|
||||
|
||||
# Kubernetes Health Checks in Consul on Kubernetes
|
||||
# Configure Health Checks for Consul on Kubernetes
|
||||
|
||||
~> This topic requires familiarity with [Kubernetes Health Checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,14 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul Service Mesh on Kubernetes
|
||||
page_title: How does Consul Service Mesh Work on Kubernetes?
|
||||
description: >-
|
||||
Consul Service Mesh is a feature built into to Consul that enables automatic
|
||||
service-to-service authorization and connection encryption across your Consul
|
||||
services. Consul Service Mesh can be used with Kubernetes to secure pod communication with
|
||||
other services.
|
||||
An injection annotation allows Consul to automatically deploy sidecar proxies on Kubernetes pods, enabling Consul's service mesh for containers running on k8s. Learn how to configure sidecars, enable services with multiple ports, change default injection settings.
|
||||
---
|
||||
|
||||
# Consul Service Mesh on Kubernetes
|
||||
# How does Consul Service Mesh Work on Kubernetes?
|
||||
|
||||
[Consul Service Mesh](/docs/connect) is a feature built into to Consul that enables
|
||||
automatic service-to-service authorization and connection encryption across
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Ingress Controller Integrations
|
||||
description: Configuring Ingress Controllers With Consul On Kubernetes
|
||||
page_title: Configure Ingress Controllers for Consul on Kubernetes
|
||||
description: >-
|
||||
Ingress controllers are pluggable components that must be configured in k8s in order to use the Ingress resource. Learn how to deploy sidecars with the controller to secure its communication with Consul, review common configuration issues, and find links to example configurations.
|
||||
---
|
||||
|
||||
# Configuring Ingress Controllers with Consul on Kubernetes
|
||||
# Configure Ingress Controllers for Consul on Kubernetes
|
||||
|
||||
-> This topic requires familiarity with [Ingress Controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Ingress Gateways - Kubernetes
|
||||
description: Configuring Ingress Gateways on Kubernetes
|
||||
page_title: Configure Ingress Gateways for Consul on Kubernetes
|
||||
description: >-
|
||||
Ingress gateways listen for external requests and route authorized traffic to instances in the service mesh running on Kubernetes. Learn how to configure ingress gateways, set intentions, and connect them to k8s applications.
|
||||
---
|
||||
|
||||
# Ingress Gateways on Kubernetes
|
||||
# Configure Ingress Gateways for Consul on Kubernetes
|
||||
|
||||
-> 1.9.0+: This feature is available in Consul versions 1.9.0 and higher
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Terminating Gateways - Kubernetes
|
||||
description: Configuring Terminating Gateways on Kubernetes
|
||||
page_title: Configure Terminating Gateways for Consul on Kubernetes
|
||||
description: >-
|
||||
Terminating gateways send secure requests from the service mesh to locations outside of the Kubernetes cluster. Learn how to configure terminating gateways for k8s, register external services in Consul’s service catalog, and define external sources as upstreams in your service mesh.
|
||||
---
|
||||
|
||||
# Terminating Gateways on Kubernetes
|
||||
# Configure Terminating Gateways for Consul on Kubernetes
|
||||
|
||||
Adding a terminating gateway is a multi-step process:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue