Global Visibility and Control for Consul
summary
Announces a hosted HCP management plane that aggregates self‑managed and HCP Consul clusters, shows service catalogs, instance counts and health across clusters, and bootstraps remote Kubernetes clusters via a provided auth blob and kubectl flow. Demonstrates that service and instance visibility requires Consul 1.14, that federation shares keys and imposes global constraints while cluster pairing avoids shared keys, and that a tech preview on HCP debuts end of month to reduce operational overhead and simplify multi‑cluster workflows.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 2:28Problem space and trends
- 10:45Operational complexity factors
- 17:27Team roles and needs
- 19:32Federation vs cluster pairing
- 21:42Vision for global visibility
- 24:33Demo overview
- 25:34Demo workflow for platform ops
- 28:49Day two operations and policies
- 31:56Discovering services across clusters
- 32:59Summary and future roadmap
related talks
34mHashiConf Europe 2022 Day 2 Keynote
49mEnterprise service networking with HashiCorp Consul and AWS (PRT238)
15mLightning Talk: Automate and Secure Consul Service Mesh on AWS ECS
22mConsul Roadmap
53mService mesh across hybrid infrastructure
44mStretching the Service Mesh Beyond the Clouds
29mBuilding for massive scale and security with the HashiCorp Cloud Platform
34mHashiCorp Boundary: Then & Now