From 93109a2d30b52d69cc9567b854ca7fa000de9742 Mon Sep 17 00:00:00 2001 From: Nicholas Richu <105801716+nrichu-hcp@users.noreply.github.com> Date: Mon, 13 Feb 2023 16:37:08 -0500 Subject: [PATCH] Update website/content/docs/connect/dataplane/index.mdx Co-authored-by: Tu Nguyen --- website/content/docs/connect/dataplane/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/connect/dataplane/index.mdx b/website/content/docs/connect/dataplane/index.mdx index eaab9bce78..9c097d79db 100644 --- a/website/content/docs/connect/dataplane/index.mdx +++ b/website/content/docs/connect/dataplane/index.mdx @@ -38,7 +38,7 @@ As a result, small deployments require fewer resources overall. For deployments **Simplified set up**: Because there are no client agents to engage in gossip, you do not have to generate and distribute a gossip encryption key to agents during the initial bootstrapping process. Securing agent communication also becomes simpler, with fewer tokens to track, distribute, and rotate. **Additional environment and runtime support**: Consul on Kubernetes versions *prior* to 1.0 (Consul 1.14) require using hostPorts and DaemonSets for client agents, which limits Consul’s ability to be deployed in environments where those features are not supported. -As of Consul on Kubernetes version 1.0 (Consul 1.14) with the new Consul Dataplane, hostPorts are no longer required and Consul now supports AWS Fargate and GKE Autopilot. +As of Consul on Kubernetes version 1.0 (Consul 1.14) with the new Consul Dataplane, `hostPorts` are no longer required and Consul now supports AWS Fargate and GKE Autopilot. **Easier upgrades**: With Consul Dataplane, updating Consul to a new version no longer requires upgrading client agents. Consul Dataplane also has better compatibility across Consul server versions, so the process to upgrade Consul servers becomes easier.