Using Consul Terraform Sync

Показать описание

Consul-Terraform-Sync (CTS) is meant to synchronize changes detected by Consul services to external network devices that do not integrate with Consul. In this iteration, Consul is leveraging the providers from Terraform to initiate changes on network devices. A common operation might be adding entries to a load balancer when a service is turned up or changed.

In the demo we'll get CTS running on an Azure VM and have it make changes on an F5 BIG-IP load balancer based off a web service registered with Consul.

-----------------------------------------------------------------------------------------------------

Music by Evan Williams ©2020

Intro 0:00
Setting the stage for CTS 2:09
How does CTS work? 3:35
Demonstration Environment 7:30
Reviewing the Terraform Configuration 10:42
Prepping the F5 BIG-IP 24:26
Running CTS 28:36
CTS Demo Summary 32:57
Outro 34:09

Рекомендации по теме

Комментарии

Great to have TF Tue back! TY Ned! Any plans to include packer in the future video? Maybe even wrap TF+Packer+ADO pipeline as a new taco recipe :) ?

mosksky

Can you make a video on rolling upgrade of an environment (VM images in particular) without requiring auto-scaling group hacks? The solution should work just as fine WITH and WITHOUT auto-scaling groups, so relying on provisioners is a no go.
We have quite a traditional environment setup (long running app-servers, etc) and are using Terraform for the AWS infrastructure (VPC, subnets, VPN, SG/ACL, etc) but have kind of avoided using it for upgrading VMs (past the initial creation). The reason is simple; there is no way (that I know of) in Terraform to ensure that the new instance is ready/configured/deployed before it moves onto the next instance, whether create-before-destroy is used or not. This has the potential to replace all the instances and end up with no applications running until ansible/k8s/nomad/whatever catches up.
Today I kind of change AMI images in stages for different server groups/AZs in some kind of manual hybrid blue-green/canary model. I'm thinking of using CDK to automate that process and some kind of integration with Consul to check health/readiness if it is safe to move on to the next group.
Any thoughts for us paranoid people?

ddanielsandberg

Using Consul Terraform Sync

Getting Started with Consul Terraform Sync English

Demo: Consul-Terraform-Sync

Using Consul Terraform Sync

Consul Terraform Sync - Awesome Use Cases

Demo: Consul-Terraform-Sync for NXS-T

Learn how to use Consul-Terraform-Sync to Automatically Provision Infrastructure. Ep 57.

{French} Getting started with Consul-Terraform-Sync

Consul Terraform Sync - Awesome Use Cases

Pushing Updates to BIG-IP w/ Consul Terraform Sync

A10 & HashiCorp Network Infrastructure Automation with Consul-Terraform-Sync

Consul Terraform Sync Enterprise

Network Security Automation with Cisco Secure Firewall & Hashicorp's Consul-Terraform-Sync

Infrastructure Keynote: Provisioning & Network Automation with Consul-Terraform-Sync

Using Consul NIA and Terraform Sync to Deploy Changes to Traditional Infrastructure

Dynamic Networking with Consul-Terraform-Sync for Terraform Enterprise and Citrix ADC

Network Automation: Consul and Terraform

Getting into HashiCorp Consul, Part 13: Consul-Terraform-Sync

Community Office Hours: Consul-Terraform-Sync

REDtalks.live #69 – Network Infrastructure Automation w/ Consul-Terraform-Sync

REDtalks.live #70 - HashiCorp's Consul Terraform Sync - Under the hood

Terraform and Consul Integration - HashiCorp Terraform Associate (003)

Network Security Automation with HashiCorp Consul-Terraform-Sync and Palo Alto Networks

Simplify Hybrid Cloud SecOps with Fortinet and Consul-Terraform-Sync for Terraform Enterprise

Achieving Networking Infrastructure Automation with HashiCorp Consul at Workday