Vault and the Kubernetes Secrets Engine

In this session, you’ll learn how to give your deployment tools the least amount of privilege required for Kubernetes. Throw away the long lived service accounts and generate on-demand, short lived, least privileged access. Learn more → learn.hashicorp.com/
Speaker: Jamie Wright, Sr. Solutions Engineer, HashiCorp
Subscribe to our RUclips Channel → ruclips.net/user/HashiCorp?s...
HashiCorp provides infrastructure automation software for multi-cloud environments, enabling enterprises to unlock a common cloud operating model to provision, secure, connect, and run any application on any infrastructure. HashiCorp open source tools Vagrant, Packer, Terraform, Vault, Consul, Nomad, Boundary, and Waypoint allow organizations to deliver applications faster by helping enterprises transition from manual processes and ITIL practices to self-service automation and DevOps practices.
For more information → hashicorp.com
Twitter → / hashicorp
LinkedIn → / hashicorp
Facebook → / hashicorp

[@EternalATomik]

Thank for this nice introduction to dynamic SA using k8s auth engine. Quick question: Why is the kubernetes provider configured with "insecure" set to "true" ?

[@HashiCorp]

In this demo we set the Kubernetes provider attribute:
insecure = true
so that it ignores the self-signed certificates from the Kubernetes API. In a real world environment we would have configured a valid certificate on the Kubernetes API and configured the Terraform provider to trust this certificate authority. Learn more about the Kubernetes provider here → registry.terraform.io/providers/hashicorp/kubernetes/latest/docs#insecure