Abstract In this blog post, we’ll explore the common sources of friction that teams encounter when writing, deploying, supporting, and securing applications. We’ll examine various personas within a team and discuss how the HashiCorp stack, comprising Terraform, Vault, and Consul, can help alleviate these challenges and foster a high-functioning, content team. Introduction Friction is an ever-present challenge in the world of software development and IT operations. In today’s interconnected IT landscape, teams across various domains face a multitude of hurdles when it comes to writing, deploying, supporting, and securing applications and systems.

Managing infrastructure with Terraform can be a breeze when everything goes according to plan. However, we all know that the dreaded “something” can and will go wrong, especially when working with complex infrastructures. In these cases, it’s essential to have a plan in place for managing Terraform state in a break glass scenario. This is particularly important when your Terraform state is managed by Terraform Cloud or Enterprise. In this blog post, we will discuss how to manage Terraform state when something goes wrong during a Kubernetes cluster deployment using Terraform and a Helm chart.