/docs/k8s/crds

This commit is contained in:
boruszak 2022-09-14 17:20:05 -05:00
parent dc66e10e71
commit 2a70eef7c8
2 changed files with 6 additions and 8 deletions

View File

@ -1,13 +1,11 @@
---
layout: docs
page_title: Consul Custom Resource Definitions
page_title: Custom Resource Definitions for Consul on Kubernetes
description: >-
Consul supports managing configuration entries via Kubernetes Custom Resources.
These custom resource can be used to manage the configuration for workloads
deployed within the cluster.
Consul on Kubernetes supports Consul's configuration entry kind through Custom Resource Definitions (CRDs). Learn how to configure Helm charts to enable CRDs and use kubectl to create, manage, and delete mesh components like gateways and intentions on k8s.
---
# Custom Resource Definitions
# Custom Resource Definitions (CRDs) for Consul on Kubernetes
This topic describes how to manage Consul [configuration entries](/docs/agent/config-entries)
via Kubernetes Custom Resources. Configuration entries provide cluster-wide defaults for the service mesh.

View File

@ -1,11 +1,11 @@
---
layout: docs
page_title: Upgrade An Existing Cluster to CRDs
page_title: Upgrade Existing Clusters to Use Custom Resource Definitions
description: >-
Upgrade an existing cluster to use custom resources.
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.
---
# Upgrade An Existing Cluster to CRDs
# Upgrade Existing Clusters to Use Custom Resource Definitions
Upgrading to consul-helm versions >= `0.30.0` will require some changes if
you utilize the following: