--- title: Gateway for SSH and Kubernetes | daily.dev description: Teleport 3.0 adds native Kubernetes support, turning it into a unified authentication and audit gateway for both SSH and Kubernetes clusters. Users can log in... canonical: https://daily.dev/posts/gateway-for-ssh-and-kubernetes-ihzj2y4xt twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Gateway for SSH and Kubernetes | daily.dev og:description: Teleport 3.0 adds native Kubernetes support, turning it into a unified authentication and audit gateway for both SSH and Kubernetes clusters. Users can log in... og:url: https://daily.dev/posts/gateway-for-ssh-and-kubernetes-ihzj2y4xt og:image: https://api.daily.dev/og/posts/ihzJ2Y4xt.png og:image:alt: Gateway for SSH and Kubernetes og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Gateway for SSH and Kubernetes **[Teleport](https://daily.dev/sources/teleport)** · 5 min read · 0 upvotes · 0 comments ## Summary Teleport 3.0 adds native Kubernetes support, turning it into a unified authentication and audit gateway for both SSH and Kubernetes clusters. Users can log in once via tsh login and get certificates that work for both ssh and kubectl commands, with synchronized RBAC roles and session recording extended to kubectl exec. The release also lets admins fine-tune cipher suites, documents monitoring endpoints, and removes a limit on trusted clusters behind SSO. A key upgrade warning: Teleport 3.0 drops legacy v2.x etcd API support, so etcd must be version 3.0 or newer before upgrading. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What do I need to check before upgrading Teleport to version 3.0 if I use the etcd backend? Before upgrading to Teleport 3.0, confirm the etcd backend is running version 3.0 or newer, because Teleport 3.0 drops support for the legacy etcd v2.x API. Upgrading with an older etcd version will break the backend integration, so verifying etcd's version first is required before proceeding with the recommended Teleport upgrade procedure. _daily.dev surfaces upgrade warnings like this so infrastructure teams avoid breaking changes during version bumps._ ### How does Teleport 3.0 let a single login work for both SSH and kubectl access? Teleport 3.0 introduces native Kubernetes support so a single tsh login command authenticates a user against a Teleport proxy and issues both an SSH certificate and a Kubernetes certificate retrieved via the Kubernetes CSR API. This lets one authentication step grant access to ssh nodes and kubectl commands, with RBAC roles kept synchronized across both systems. _developers comparing unified access gateways for ssh and kubernetes can track releases like this on daily.dev._ --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#ssh](https://daily.dev/tags/ssh) [View this post on daily.dev](https://daily.dev/posts/gateway-for-ssh-and-kubernetes-ihzj2y4xt) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Gateway for SSH and Kubernetes","url":"https://daily.dev/posts/gateway-for-ssh-and-kubernetes-ihzj2y4xt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/gateway-for-ssh-and-kubernetes-ihzj2y4xt"},"datePublished":"2026-08-23T12:22:05.931Z","dateModified":"2026-08-23T12:47:47.633Z","description":"Teleport 3.0 adds native Kubernetes support, turning it into a unified authentication and audit gateway for both SSH and Kubernetes clusters. Users can log in...","image":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","thumbnailUrl":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/gateway-for-ssh-and-kubernetes-ihzj2y4xt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,ssh","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"Gateway for SSH and Kubernetes"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/gateway-for-ssh-and-kubernetes-ihzj2y4xt#faq","mainEntity":[{"@type":"Question","name":"What do I need to check before upgrading Teleport to version 3.0 if I use the etcd backend?","acceptedAnswer":{"@type":"Answer","text":"Before upgrading to Teleport 3.0, confirm the etcd backend is running version 3.0 or newer, because Teleport 3.0 drops support for the legacy etcd v2.x API. Upgrading with an older etcd version will break the backend integration, so verifying etcd's version first is required before proceeding with the recommended Teleport upgrade procedure. daily.dev surfaces upgrade warnings like this so infrastructure teams avoid breaking changes during version bumps."}},{"@type":"Question","name":"How does Teleport 3.0 let a single login work for both SSH and kubectl access?","acceptedAnswer":{"@type":"Answer","text":"Teleport 3.0 introduces native Kubernetes support so a single tsh login command authenticates a user against a Teleport proxy and issues both an SSH certificate and a Kubernetes certificate retrieved via the Kubernetes CSR API. This lets one authentication step grant access to ssh nodes and kubectl commands, with RBAC roles kept synchronized across both systems. developers comparing unified access gateways for ssh and kubernetes can track releases like this on daily.dev."}}]} ```