Hello Teleport Community,
Along with my favorite folk festival, Oktoberfest, October also marks a lot of Kubernetes-related activities for our team. Myself and a large team of Teleporters will be at KubeCon. We’ll be speaking about Teleport Machine ID, at a booth and also hosting a Happy Hour.
Teleport Kubernetes updates
Kubernetes Access support to Teleport Connect
Teleport Connect is a developer-friendly browser for cloud infrastructure. Unlike other terminals, Teleport Connect is designed to be optimized for identity-based access for devs working in the cloud. For more information, see our release notes about 10.3, and download Connect for Mac, Linux and Windows.
Helm Chart updates
Updated Helm Charts to support Kubernetes v1.25
Kubernetes Operator
The Teleport Kubernetes Operator provides a way for Kubernetes users to manage some Teleport resources through Kubernetes, following the Operator Pattern.
The Teleport Kubernetes Operator is deployed alongside its custom resource definitions. Once deployed, users can use a Kubernetes client like kubectl or their existing CI/CD Kubernetes pipelines to create Teleport custom resources. The Teleport Kubernetes Operator watches for those resources and makes API calls to Teleport to reach the desired state.
Currently supported Teleport resources are:
– Users
– Roles
Learn more about the Teleport Kubernetes Access – Kubernetes Operator.
Kubernetes support for Machine ID
Added in Teleport 10.1, Machine ID now supports Kubernetes and Application Access. We’ll be doing a deeper dive into Kubernetes with our CloudNative Security Conference talk by Kenneth DuMez, “Why Machines Deserve Rights: Rethinking Automated Infrastructure Access with OSS Teleport Machine ID”, but if you like to dive straight in, you can try our Machine ID Getting Started Guide.
This wraps up this week’s newsletter for Teleport Kubernetes Access. If you would like to learn more about large Teleport deployments, I would recommend joining us for Teleport Connect 22.
