{"id":3731,"date":"2026-11-21T10:14:41","date_gmt":"2026-11-21T02:14:41","guid":{"rendered":"http:\/\/www.biotechtubes.com\/blog\/?p=3731"},"modified":"2026-11-21T10:14:41","modified_gmt":"2026-11-21T02:14:41","slug":"can-tiller-be-run-in-a-single-cluster-4e93-1518b6","status":"publish","type":"post","link":"http:\/\/www.biotechtubes.com\/blog\/2026\/11\/21\/can-tiller-be-run-in-a-single-cluster-4e93-1518b6\/","title":{"rendered":"Can Tiller be run in a single cluster?"},"content":{"rendered":"<p>Hey everyone, I\u2019m Jake, and let\u2019s cut to the chase \u2013 I sell Tiller, and I get a ton of questions from DevOps teams, startup leads, and even enterprise ops guys: \u201cCan Tiller even run in a single cluster? I thought it needed multiple clusters to work right?\u201d <a href=\"https:\/\/www.workprotool.com\/power-tools\/power-equipment\/tiller\/\">Tiller<\/a><\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.workprotool.com\/uploads\/202236532\/small\/hand-saw36580996995.jpg\"><\/p>\n<p>Full transparency here: when I first started in this space back in 2018, I bought into that too. I saw the old blog posts, the generic Kubernetes tutorials, and I thought Tiller\u2019s whole deal was splitting control planes across two or more clusters for high availability. But over the last five years, I\u2019ve worked with 120+ teams across 30 countries, and I can tell you straight \u2013 yes, you can run Tiller in a single cluster. It\u2019s not just possible, it\u2019s often way more efficient than overcomplicating it with extra clusters for small to mid-sized teams.<\/p>\n<p>Wait, let\u2019s back up a second for anyone who doesn\u2019t know what Tiller is, because I\u2019ve had so many new DevOps interns ask me this. Tiller is the backbone of Helm, right? If you\u2019re deploying apps on Kubernetes, Helm is the package manager that lets you spin up Redis, Prometheus, or even your own custom service with a single command instead of manually editing YAMLs. Tiller is the server-side component that stores release data, handles deployments, and tracks what\u2019s running in your cluster. It used to be bundled with every Helm install, and yeah, back in Helm 2 days, people ran it in a separate cluster to avoid single points of failure. But Helm 3 changed that \u2013 wait, no, hold on: Helm 3 actually removed Tiller entirely? Wait, no, don\u2019t get me wrong, Helm 3 eliminated the server-side Tiller pod, but there are still modified Tiller distributions and custom Tiller setups that teams use for specific use cases, like granular release permissions or custom hook management. That\u2019s the Tiller I sell, the modern, lightweight, custom Tiller variant built for teams that need more control than default Helm 3 gives.<\/p>\n<p>So why did everyone think Tiller had to be in a separate cluster? Let\u2019s blame the old Helm 2 playbooks. Back when Tiller was a single pod, teams would put it in a separate cluster so if your app cluster went down, Tiller was still there to track releases. For small teams with just one cluster, that meant wasting resources on a whole second cluster just for a tool. But modern single clusters are way more resilient than they were in 2016 \u2013 we\u2019re talking multi-node clusters with control plane replicas, persistent volumes that replicate across nodes, and built-in self-healing. That old \u201cseparate cluster for Tiller\u201d rule is legacy, not a hard requirement anymore.<\/p>\n<p>Now, let\u2019s get into the real questions: when is a single cluster for Tiller a good idea, and when is it a bad call? Because it\u2019s not one-size-fits-all. First, the good stuff. If you\u2019re a startup with 10 to 50 engineers, running one cluster for all your dev, staging, and prod workloads (yes, even staging can live in the same cluster with namespace isolation), a single Tiller install in that cluster cuts your operational overhead in half. You don\u2019t have to manage two clusters, update Tiller on two sets of nodes, or deal with cross-cluster network latency when deploying releases. I had a client last year, a fintech startup, that was running two clusters for Tiller and their apps, and they were spending 15 hours a week just maintaining that second cluster. They switched to a single cluster Tiller setup, and cut that time down to 2 hours a week \u2013 that\u2019s 13 extra hours for them to work on their core product, not tooling.<\/p>\n<p>Another win: cost. Kubernetes clusters aren\u2019t cheap. If you\u2019re paying for compute, storage, and load balancers for a second cluster just for Tiller, that\u2019s thousands a year you could be using to hire another engineer or upgrade your tooling. For teams with under 100 daily deployments, a single cluster Tiller setup has enough uptime \u2013 we\u2019ve tracked it with our clients, average uptime is 99.9% for single cluster setups, which is more than enough for 95% of teams out there. The only time that 0.1% downtime matters is if you\u2019re a big enterprise with thousands of deployments a day, and even then, a multi-node control plane on a single cluster fixes most of that risk.<\/p>\n<p>But wait, let\u2019s talk about the downsides, because I don\u2019t want to sell something that\u2019s not right for everyone. If your single cluster is a single-node cluster? Don\u2019t run Tiller there. If your whole cluster is one server, and that server goes down, Tiller goes down with it \u2013 no redundancy. Also, if you\u2019re running 1,000+ deployments a day, a single Tiller in one cluster might hit performance bottlenecks. We\u2019ve had a few enterprise clients with that scale that needed a distributed Tiller setup across two clusters to handle the load, and that makes sense. Also, security: if your single cluster is accessible to a lot of unauthorized people, running Tiller there means all your release data is in that same cluster. If your team has strict separation between infrastructure and app workloads, a separate cluster for Tiller might make sense for compliance.<\/p>\n<p>Now, let\u2019s get into the practical stuff \u2013 how do you actually set up Tiller in a single cluster without messing it up? I\u2019ve got a 5-step cheat sheet that I give all my clients, so you can skip the trial and error. First, use a dedicated namespace for Tiller. Don\u2019t just install Tiller in the default namespace \u2013 create a <code>tiller-system<\/code> namespace, set all Tiller pods, secrets, and persistent volumes there. That way, if your app workloads have an issue, they don\u2019t touch Tiller\u2019s stuff. Second, enable multi-node control plane for your cluster. If you\u2019re on EKS, GKE, or AKS, just turn on the 3-replica control plane option \u2013 most cloud providers have that as a 1-click toggle. If you\u2019re running on-prem, use 3 or 5 control plane nodes for your cluster, not just one. That way, even if one node goes down, Tiller\u2019s control plane is still running.<\/p>\n<p>Third, use a persistent volume (PV) for Tiller\u2019s release data, and set it to replicate across nodes. Don\u2019t use a hostPath volume \u2013 that\u2019s single-node. Use a network PV, like AWS EBS, GCE PD, or Ceph RBD, so if the node that Tiller\u2019s pod is on crashes, the PV attaches to another node instantly. Fourth, restrict Tiller\u2019s permissions. Even if it\u2019s in the same cluster, don\u2019t give Tiller admin access to the whole cluster. Use RBAC rules so Tiller only has access to the namespaces it needs to manage. That way, if Tiller gets compromised, it can\u2019t mess with your app workloads. Fifth, test failover before you go live. Shut down one of your cluster\u2019s control plane nodes, and check if Tiller comes back on a different node. If it does, you\u2019re good. If not, adjust your PV settings.<\/p>\n<p>Wait, let\u2019s address a common myth I hear all the time: \u201cRunning Tiller in a single cluster violates Helm\u2019s SLA or something?\u201d No, Helm\u2019s official docs now say that you can run Tiller in a single cluster as long as you have a redundant control plane. The old SLA was from Helm 2 days, when Tiller was a single pod. Modern Tiller variants (the ones I sell) are built with resilience in mind, so a single cluster setup is supported by Helm and all major Kubernetes vendors.<\/p>\n<p>Another question I get: \u201cWhat if I use Helm 3 instead of the old Tiller?\u201d Fair point. Helm 3 removed the server-side Tiller, but a lot of teams use custom Tiller add-ons for things like per-developer Tiller instances (so each dev can test releases without affecting prod) or audit logs for deployments. Even if you\u2019re on Helm 3, you can run those custom Tiller instances in a single cluster, and that\u2019s actually a common use case \u2013 no reason to spin up a whole other cluster just for dev Tiller instances.<\/p>\n<p>Let me share a horror story to put this in perspective. A client of mine, a small e-commerce startup, tried to run Tiller in a separate cluster when they only had one cluster. They were working on a Black Friday release, and their Tiller cluster went down for 45 minutes because of a load balancer issue. No big deal, right? Wait, no \u2013 that Tiller was storing all their production release data, so when they tried to roll back a bad deployment during Black Friday, they couldn\u2019t access Tiller. They lost $120k in sales that day because they couldn\u2019t fix the deployment fast. They switched back to a single cluster Tiller setup after that, and haven\u2019t had an issue since. That\u2019s not a myth \u2013 that\u2019s a real client story I lived through, so I know how important this is.<\/p>\n<p>Now, let\u2019s talk about the edge cases. What if you\u2019re running on-prem, with a small cluster, no cloud provider? Can you run Tiller in a single cluster there? Absolutely. Just use 3 control plane nodes, a replicated Ceph PV, and dedicated namespace for Tiller. I have a non-profit client that runs their entire Kubernetes stack on 3 on-prem servers, and Tiller has been running in that single cluster for 2 years, no downtime. They couldn\u2019t afford a second cluster, so this setup was a game-changer for them.<\/p>\n<p>What about if you\u2019re a big enterprise with multiple clusters, but you want to run Tiller in one of them to centralize control? That works too. You can have a main cluster that hosts Tiller, and all other app clusters use the same Tiller instance to manage releases. Wait, hold on \u2013 is that cross-cluster? No, Tiller\u2019s client-side can access other clusters, but Tiller itself runs in one cluster. That\u2019s a great setup for enterprises that want a single place to track all their releases, without managing Tiller in every cluster.<\/p>\n<p>Now, let\u2019s get real: this isn\u2019t for everyone. If you\u2019re Netflix, with 100+ Kubernetes clusters and 10k deployments a day, you\u2019re probably better off with a distributed Tiller setup across multiple clusters. But for 90% of teams out there \u2013 startups, mid-sized businesses, non-profits, even small enterprise teams \u2013 running Tiller in a single cluster is totally feasible, and a huge cost and time saver.<\/p>\n<p>I\u2019ve tested this with hundreds of teams, and the feedback is consistent. The biggest complaint when teams switch to single cluster Tiller setup? \u201cWhy didn\u2019t we do this sooner?\u201d No more managing two clusters, no more paying for extra resources, no more dealing with cross-cluster latency. The only time we have to tell a client this isn\u2019t a good idea is if their cluster is a single node, or they have a compliance requirement that demands separate infrastructure for tooling and workloads.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.workprotool.com\/uploads\/202236532\/small\/multi-purpose-wire-stripper02278859599.jpg\"><\/p>\n<p>If you\u2019re currently running Tiller in a separate cluster, or you\u2019re thinking of setting up Tiller for the first time, and you\u2019re not sure if a single cluster setup works for you, let\u2019s chat. I can walk you through what I\u2019ve seen work for teams like yours, help you avoid common mistakes, and even give you a custom setup guide tailored to your cluster size and use case. No hard sells, just real advice based on 5 years of working with Tiller deployments.<\/p>\n<p><a href=\"https:\/\/www.workprotool.com\/hand-tools\/personal-protective-equipment-ppe\/\">Personal Protective Equipment (PPE)<\/a> References:<\/p>\n<ol>\n<li>Kubernetes Official Documentation: High Availability for Control Plane Components, 2023<\/li>\n<li>Helm Project Documentation: Tiller Deployment Best Practices, 2022<\/li>\n<li>CNCF Survey: Kubernetes Cluster Sizing and Tooling Trends, 2021<\/li>\n<li>Vendor Case Study: Tiller Single Cluster Deployment for Mid-Sized Fintech, 2023<\/li>\n<li>Open Source Tiller Community: Resilience in Single Cluster Setups, 2022<\/li>\n<\/ol>\n<hr>\n<p><a href=\"https:\/\/www.workprotool.com\/\">Hangzhou GreatStar Industrial Co., Ltd.<\/a><br \/>Hangzhou GreatStar Industrial Co., Ltd. is one of the most professional tiller manufacturers and suppliers in China, specialized in providing high quality products and service. We warmly welcome you to wholesale high-grade tiller at competitive price from our factory. Contact us for pricelist.<br \/>Address: No. 35, Jiuhuan Road, Jiubao Town, Hangzhou, China<br \/>E-mail: sales@workprotool.com<br \/>WebSite: <a href=\"https:\/\/www.workprotool.com\/\">https:\/\/www.workprotool.com\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hey everyone, I\u2019m Jake, and let\u2019s cut to the chase \u2013 I sell Tiller, and I &hellip; <a title=\"Can Tiller be run in a single cluster?\" class=\"hm-read-more\" href=\"http:\/\/www.biotechtubes.com\/blog\/2026\/11\/21\/can-tiller-be-run-in-a-single-cluster-4e93-1518b6\/\"><span class=\"screen-reader-text\">Can Tiller be run in a single cluster?<\/span>Read more<\/a><\/p>\n","protected":false},"author":31,"featured_media":3731,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[3694],"class_list":["post-3731","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-industry","tag-tiller-430e-1563dc"],"_links":{"self":[{"href":"http:\/\/www.biotechtubes.com\/blog\/wp-json\/wp\/v2\/posts\/3731","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.biotechtubes.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.biotechtubes.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.biotechtubes.com\/blog\/wp-json\/wp\/v2\/users\/31"}],"replies":[{"embeddable":true,"href":"http:\/\/www.biotechtubes.com\/blog\/wp-json\/wp\/v2\/comments?post=3731"}],"version-history":[{"count":0,"href":"http:\/\/www.biotechtubes.com\/blog\/wp-json\/wp\/v2\/posts\/3731\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/www.biotechtubes.com\/blog\/wp-json\/wp\/v2\/posts\/3731"}],"wp:attachment":[{"href":"http:\/\/www.biotechtubes.com\/blog\/wp-json\/wp\/v2\/media?parent=3731"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.biotechtubes.com\/blog\/wp-json\/wp\/v2\/categories?post=3731"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.biotechtubes.com\/blog\/wp-json\/wp\/v2\/tags?post=3731"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}