From 1367b1b70c4f286d34eb00eb522ffba0c7f5a8e6 Mon Sep 17 00:00:00 2001 From: David Yu Date: Wed, 21 Feb 2024 15:58:04 -0800 Subject: [PATCH] Update install.mdx --- .../content/docs/k8s/installation/install.mdx | 24 ++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/website/content/docs/k8s/installation/install.mdx b/website/content/docs/k8s/installation/install.mdx index 35eefff333..f7fe29dc30 100644 --- a/website/content/docs/k8s/installation/install.mdx +++ b/website/content/docs/k8s/installation/install.mdx @@ -114,7 +114,29 @@ global: enabled: true ``` -Refer to [`openshift` in the Helm chart reference](/consul/docs/k8s/helm#v-global-openshift) for additional information. +Refer to [`openshift` in the Helm chart reference](/consul/docs/k8s/helm#v-global-openshift) and [Deploy Consul on RedHat OpenShift](https://developer.hashicorp.com/consul/tutorials/kubernetes/kubernetes-openshift-red-hat) for additional information. + +### Install Consul on GKE Autopilot + +GKE Autopilot provides a fully managed environment for containerized workloads and requires the Consul CNI Plugin to be installed. Refer to [Enable the Consul CNI plugin](#enable-the-consul-cni-plugin) for a full reference on how to enable the CNI plug-in. By default, GKE Autopilot also installs [Gateway API](https://gateway-api.sigs.k8s.io) resources, so it is recommended to customize the `connectInject.apiGateway` stanza to accomodate for the pre-installed Gateway API CRDs. Below is a working example that enables both Consul Service Mesh and Consul API Gateway on GKE Autopilot. + + + + ```yaml + global: + name: consul + connectInject: + enabled: true + apiGateway: + manageExternalCRDs: false + manageNonStandardCRDs: true + cni: + enabled: true + logLevel: info + cniBinDir: "/home/kubernetes/bin" + cniNetDir: "/etc/cni/net.d" + ``` + ### Enable the Consul CNI plugin