mirror of https://github.com/hashicorp/consul
Update website/content/docs/connect/dataplane/index.mdx
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>pull/16247/head
parent
54a573a7d5
commit
93109a2d30
|
@ -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.
|
||||
|
||||
|
|
Loading…
Reference in New Issue