A Hands-on Approach to Consul Deployment Strategies in a Hybrid Environment
summary
Deploys a single Consul datacenter that mixes VM-hosted servers and Kubernetes-hosted clients, exemplified by one VM server and a four-node cluster that successfully joins as clients. Uses an Ansible role to install and configure Consul servers, the consul Helm chart to run the agent as a DaemonSet and Consul Connect inject, and standard ACLs. Requires routable, non‑overlapping pod IPs and open gossip port 8301, notes Kubernetes 1.24’s manual service account token handling, and recommends 3–5 servers for HA.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 1:50Industry trends and microservices
- 5:25What is Consul and its evolution
- 9:56How Consul works and architecture
- 10:18Consul deployment strategies
- 14:14Hands-on: Ansible setup for Consul
- 16:04Kubernetes integration with Consul
- 19:17Hybrid environment demo
- 20:01Consul service mesh features
- 21:05Conclusion and future outlook
related talks
24mDeployment Patterns for Consul in Kubernetes
22mConsul Use Cases At Stripe: Service Mesh and More
54mUsing Terraform and Consul to delegate service deployment to service teams
19mService Mesh and Your Legacy Apps: Connecting to Kubernetes with Consul
44mScaling Microservices with Kubernetes
26mSimplify Networking in Kubernetes with Consul and Wireguard
25mSwitching From External Load Balancing to consul & ingress [I]
37mManaging and Running Multiple Kubernetes Clusters in Hybrid Setups