Skip to content

docs: improve clarity about what kubara actual is and isn't - #576

Open
tuunit wants to merge 2 commits into
mainfrom
docs/improve-clarity
Open

docs: improve clarity about what kubara actual is and isn't#576
tuunit wants to merge 2 commits into
mainfrom
docs/improve-clarity

Conversation

@tuunit

@tuunit tuunit commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

No description provided.

Signed-off-by: Jan Larwig <jan@larwig.com>
@tuunit
tuunit requested a review from a team August 20, 2026 06:55
Signed-off-by: Jan Larwig <jan@larwig.com>
@tuunit
tuunit force-pushed the docs/improve-clarity branch from 8186037 to 8f59fa3 Compare August 20, 2026 06:58
Comment thread docs/content/index.md
Helm packages and deploys one application. Kubara applies that idea to a whole Kubernetes platform.

It brings together infrastructure provisioning, multi-tenancy setup, GitOps onboarding, and essential third-party tooling in one reusable [GitOps](7_architecture/architecture_overview.md#gitops) workflow.
A kubara catalog can bundle Helm charts, Terraform modules, scripts, and the GitOps structure needed for a platform. Kubara renders that catalog into reproducible artifacts and bootstraps the initial Argo CD setup.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A kubara catalog can bundle Helm charts, Terraform modules, scripts, and the GitOps structure needed for a platform. Kubara renders that catalog into reproducible artifacts and bootstraps the initial Argo CD setup.
A kubara catalog can bundle Helm charts, Terraform modules, scripts and the GitOps structure needed for a platform. Kubara renders that catalog into reproducible artifacts and bootstraps the initial Argo CD setup.

Comment thread docs/content/index.md
kubara gives you a unified, reproducible way to deploy Kubernetes platforms with minimal effort and high consistency whether you run on cloud, edge, or hybrid infrastructure.

kubara also gives you a reusable packaging model for platform architecture: **what Helm charts are for single applications, kubara catalogs are for your platform setup**.
In short, kubara is a single-binary Go CLI for building, packaging, and bootstrapping Kubernetes platforms.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure if its really relevant that it is "single-binary", nor "Go".
I think it hinders the reading-flow for the sentence and holds information that can easily be seen through looking at the repo. But this is just personal preference :)

Comment thread docs/content/index.md
### A package manager for your platform

You can think of kubara as a package manager for platform architecture: it helps you define a reusable platform setup, generate the needed artifacts, and package that setup for reuse across many clusters.
Helm packages and deploys one application. Kubara applies that idea to a whole Kubernetes platform.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Helm packages and deploys one application. Kubara applies that idea to a whole Kubernetes platform.
Helm packages and deploys one application. kubara applies that idea to a whole Kubernetes platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants