Securing access to Kubernetes with Boundary

Learn how you can use Vault to dynamically generate Kubernetes Service Accounts for operators to log into Kubernetes via HashiCorp Boundary. Learn more about Boundary → developer.hashicorp.com/boundary
Watch Past Snapshots Demo Sessions → www.hashicorp.com/events/seri...
Subscribe to our KZbin Channel → kzbin.info?s...
For hands-on interactive labs, visit HashiCorp Developer → developer.hashicorp.com/
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

[@miggsantos]

Hi, what is the contents of the connect sh file. We are setting up Boundary OSS and got the Kubernetes connection working but not with boundary connect kube. Would be great if you could share with us how you do it.

[@mrfaifai]

The kube-api cannot really close anyway? For example if that k8s cluster need to integrate with Vault. The API need to open. Similar control should be achievable using vault only? Hopefully this kind of k8s session can be recorded in Boundary as well.

[@HashiCorp]

We would like to understand your question more deeply to give you an accurate answer, would you please drop us an email at [e-mail] so we can take this discussion further?