status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

/docs/k8s/operations

This commit is contained in:
boruszak 2022-09-14 17:29:21 -05:00
parent 0de4184b95
commit acfbda94e7
4 changed files with 16 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/content/docs/k8s/operations/certificate-rotation.mdx
View File

@ -1,10 +1,11 @@
---
layout: docs
page_title: Certificate Rotation
description: Rotate Certificate on Kubernetes Cluster safely
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.
---
# Rotating Server Certificates
# Rotate TLS Certificates for Consul on Kubernetes
As of Consul Helm version `0.29.0`, if TLS is enabled, new TLS certificates for the Consul Server
are issued every time the Helm chart is upgraded. These certificates are signed by the same CA and will

7
website/content/docs/k8s/operations/gossip-encryption-key-rotation.mdx
View File

@ -1,10 +1,11 @@
---
layout: docs
page_title: Gossip Encryption Key Rotation
description: Rotate the Gossip Encryption Key on Kubernetes Cluster safely
page_title: Rotate Gossip Encryption Keys for Consul on Kubernetes
description: >-
Consul agents use encryption keys to secure their gossip communication, and you must rotate the keys periodically to maintain network security. Learn how to use `keygen` and `keyring` commands to rotate keys for agents on k8s clusters.
---
# Rotating Gossip Encryption Key
# Rotate Gossip Encryption Keys for Consul on Kubernetes
The following instructions provides a step-by-step manual process for rotating [gossip encryption](/docs/security/encryption#gossip-encryption) keys on Consul clusters that are deployed onto a Kubernetes cluster with Consul on Kubernetes.

7
website/content/docs/k8s/operations/tls-on-existing-cluster.mdx
View File

@ -1,10 +1,11 @@
---
layout: docs
page_title: Configure TLS on an Existing Cluster
description: Configure TLS on an existing Consul cluster running in Kubernetes
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.
---
# Configuring TLS on an Existing Cluster
# Rolling Updates to TLS for Existing Clusters on Kubernetes
As of Consul Helm version `0.16.0`, the chart supports TLS for communication
within the cluster. If you already have a Consul cluster deployed on Kubernetes,

7
website/content/docs/k8s/operations/uninstall.mdx
View File

@ -1,10 +1,11 @@
---
layout: docs
page_title: Uninstall
description: Uninstall Consul on Kubernetes
page_title: Uninstall Consul on Kubernetes
description: >-
You can use the Consul-K8s CLI tool to remove all or part of a Consul installation on Kubernetes. You can also use Helm and then manually remove resources that Helm does not delete.
---
# Uninstall Consul
# Uninstall Consul on Kubernetes
You can uninstall Consul using Helm commands or the Consul K8s CLI.