--- title: Stop Rebuilding Your Kubernetes Platform: How kubara... description: kubara is a tool that packages reusable Kubernetes platform architecture through catalogs, rather than individual application charts like Helm. A built-in... canonical: https://daily.dev/posts/stop-rebuilding-your-kubernetes-platform-how-kubara-catalogs-make-architecture-reusable-xemppzuox twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Stop Rebuilding Your Kubernetes Platform: How kubara Catalogs Make Architecture Reusable | daily.dev og:description: kubara is a tool that packages reusable Kubernetes platform architecture through catalogs, rather than individual application charts like Helm. A built-in... og:url: https://daily.dev/posts/stop-rebuilding-your-kubernetes-platform-how-kubara-catalogs-make-architecture-reusable-xemppzuox og:image: https://api.daily.dev/og/posts/xEMPpzUoX.png og:image:alt: Stop Rebuilding Your Kubernetes Platform: How kubara Catalogs Make Architecture Reusable 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. # Stop Rebuilding Your Kubernetes Platform: How kubara Catalogs Make Architecture Reusable **[ITNEXT](https://daily.dev/sources/itnext)** · 12 min read · 1 upvotes · 0 comments ## Summary kubara is a tool that packages reusable Kubernetes platform architecture through catalogs, rather than individual application charts like Helm. A built-in catalog provides an opinionated baseline (delivery, networking, security, observability, storage, recovery), while an optional external catalog lets platform teams add organization-specific services without modifying the maintained baseline. config.yaml expresses cluster-specific intent, and kubara generates platform-components and platform-configs that Git and Argo CD reconcile. A worked example walks through building an external catalog with vCluster, vCluster Platform, Sveltos, and Kube Resource Orchestrator to run a load and scale test simulating 15,000 clusters and 75,000 applications at roughly a tenth of the cost of dedicated managed clusters (~€120,000 vs ~€1.2 million). The piece also covers collision handling between built-in and external service definitions, the --catalog-overwrite flag, and guidance on when to create an external catalog versus just editing config.yaml. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the difference between a Helm chart and a kubara catalog? A Helm chart packages a single application, while a kubara catalog packages an entire platform architecture: the definitions, templates, components, and configuration model needed to generate a consistent Kubernetes platform across clusters. Catalogs combine with a cluster-specific config.yaml to produce the desired state that Argo CD reconciles against Kubernetes. _daily.dev surfaces platform-engineering approaches like this for teams weighing reusable Kubernetes architecture patterns._ ### How do you handle a naming collision between a built-in and external kubara catalog service definition? kubara rejects the collision by default when a built-in and external ServiceDefinition share the same metadata.name, protecting teams from accidentally replacing a maintained definition. Overriding requires explicitly passing the --catalog-overwrite flag, and doing so should only happen after verifying the dependencies of the component being replaced, since other components may expect resources like Certificate or ServiceMonitor from it. _engineers extending Kubernetes platforms safely can track patterns like this override safeguard via daily.dev._ ### How much cheaper is it to simulate thousands of Kubernetes clusters with vCluster instead of provisioning dedicated managed clusters? Simulating 1,000 virtual clusters with vCluster to estimate capacity for 15,000 clusters and 75,000 applications cost approximately €120,000 on STACKIT, versus an estimated €1.2 million for an equivalent environment using dedicated managed Kubernetes clusters, roughly a tenfold cost reduction for the load and scale test. _teams deciding between virtual and dedicated clusters for scale testing can find cost comparisons like this on daily.dev._ ## Similar posts on daily.dev - [kubara: An Open Source Kubernetes Platform Framework Built on GitOps](https://daily.dev/posts/kubara-an-open-source-kubernetes-platform-framework-built-on-gitops-4wtpimtvb) · ITNEXT · 13 upvotes · 0 comments - [Build a Local Kubernetes Platform with kubara, kind, and Argo CD](https://daily.dev/posts/build-a-local-kubernetes-platform-with-kubara-kind-and-argo-cd-zb6ibe5zy) · ITNEXT · 4 upvotes · 0 comments - [Building platforms using kro for composition](https://daily.dev/posts/building-platforms-using-kro-for-composition-xkgeioxnq) · CNCF · 4 upvotes · 0 comments - [Beyond the Merge: Declarative Promotion Stages with Akuity Kargo and Helm](https://daily.dev/posts/beyond-the-merge-declarative-promotion-stages-with-akuity-kargo-and-helm-6nbzkxawq) · Medium · 1 upvotes · 0 comments - [Building and Scaling a Platform with Project-as-a-Service](https://daily.dev/posts/building-and-scaling-a-platform-with-project-as-a-service-j0ovlxcpr) · InfoQ · 0 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#platform-engineering](https://daily.dev/tags/platform-engineering), [#gitops](https://daily.dev/tags/gitops), [#helm](https://daily.dev/tags/helm), [#argocd](https://daily.dev/tags/argocd) [View this post on daily.dev](https://daily.dev/posts/stop-rebuilding-your-kubernetes-platform-how-kubara-catalogs-make-architecture-reusable-xemppzuox) ```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":"Stop Rebuilding Your Kubernetes Platform: How kubara Catalogs Make Architecture Reusable","url":"https://daily.dev/posts/stop-rebuilding-your-kubernetes-platform-how-kubara-catalogs-make-architecture-reusable-xemppzuox","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/stop-rebuilding-your-kubernetes-platform-how-kubara-catalogs-make-architecture-reusable-xemppzuox"},"datePublished":"2026-08-17T06:55:24.335Z","dateModified":"2026-09-13T20:09:25.635Z","description":"kubara is a tool that packages reusable Kubernetes platform architecture through catalogs, rather than individual application charts like Helm. A built-in...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d639052455e1a43fa773f0fbd584e784?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d639052455e1a43fa773f0fbd584e784?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ITNEXT","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":"ITNEXT","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/itnext2","url":"https://daily.dev/sources/itnext"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/stop-rebuilding-your-kubernetes-platform-how-kubara-catalogs-make-architecture-reusable-xemppzuox","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,platform-engineering,gitops,helm,argocd","timeRequired":"PT12M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ITNEXT","item":"https://daily.dev/sources/itnext"},{"@type":"ListItem","position":3,"name":"Stop Rebuilding Your Kubernetes Platform: How kubara Catalogs Make Architecture Reusable"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/stop-rebuilding-your-kubernetes-platform-how-kubara-catalogs-make-architecture-reusable-xemppzuox#faq","mainEntity":[{"@type":"Question","name":"What is the difference between a Helm chart and a kubara catalog?","acceptedAnswer":{"@type":"Answer","text":"A Helm chart packages a single application, while a kubara catalog packages an entire platform architecture: the definitions, templates, components, and configuration model needed to generate a consistent Kubernetes platform across clusters. Catalogs combine with a cluster-specific config.yaml to produce the desired state that Argo CD reconciles against Kubernetes. daily.dev surfaces platform-engineering approaches like this for teams weighing reusable Kubernetes architecture patterns."}},{"@type":"Question","name":"How do you handle a naming collision between a built-in and external kubara catalog service definition?","acceptedAnswer":{"@type":"Answer","text":"kubara rejects the collision by default when a built-in and external ServiceDefinition share the same metadata.name, protecting teams from accidentally replacing a maintained definition. Overriding requires explicitly passing the --catalog-overwrite flag, and doing so should only happen after verifying the dependencies of the component being replaced, since other components may expect resources like Certificate or ServiceMonitor from it. engineers extending Kubernetes platforms safely can track patterns like this override safeguard via daily.dev."}},{"@type":"Question","name":"How much cheaper is it to simulate thousands of Kubernetes clusters with vCluster instead of provisioning dedicated managed clusters?","acceptedAnswer":{"@type":"Answer","text":"Simulating 1,000 virtual clusters with vCluster to estimate capacity for 15,000 clusters and 75,000 applications cost approximately €120,000 on STACKIT, versus an estimated €1.2 million for an equivalent environment using dedicated managed Kubernetes clusters, roughly a tenfold cost reduction for the load and scale test. teams deciding between virtual and dedicated clusters for scale testing can find cost comparisons like this on daily.dev."}}]} ```