Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration with Kapitan and Commodore #649

Open
a-prokopyev-resume opened this issue Jul 13, 2024 · 1 comment
Open

Integration with Kapitan and Commodore #649

a-prokopyev-resume opened this issue Jul 13, 2024 · 1 comment
Labels
question Further information is requested

Comments

@a-prokopyev-resume
Copy link

Hello,

Please let me know, is it a good idea to try to integrate your k0smotron with Commodore which is cloud-native SCM partialy based on Kapitan?

https://syn.tools/syn/about/features.html

Multi-Cluster and Multi-Tenant Management

Keeping track of many Kubernetes clusters and knowing to which tenant each belongs to is the key job of Lieutenant. With Lieutenant an inventory service is provided, which not only keeps track of clusters and tenants, but also of other facts about clusters (cloud, location, …​). The information stored in Lieutenant is used by several other Project Syn tools, like Commodore.
Full GitOps Operations

In order for [GitOps](https://www.gitops.tech/) to unfold its full potential, some prerequisites must be met. These include a component actually implementing GitOps, and some accessible Git repositories. Project Syn makes use of [Argo CD](https://argoproj.github.io/argo-cd/) as the GitOps controller, running on each Kubernetes cluster. The Project Syn tool Lieutenant Operator manages Git repositories (creating, updating, deleting) based on Tenant and Cluster Kubernetes-CRD configuration objects.
Tooling Bootstrapping

Getting a Kubernetes cluster "Project Syn enabled" should be as easy as possible. And that’s exactly the job of Steward. This in-cluster agent is installed via Lieutenant. Upon cluster registration in Lieutenant, a one-time install URL is generated, which is easily applicable to any Kubernetes cluster. Once Steward is running on the cluster, it bootstraps Argo CD, generates a deploy SSH key, sends it to Lieutenant and configures Argo CD with the information available in Lieutenant, so that Argo CD can do its job.

and more ...

It seems they integrate with K3S/K3D. But I prefer your K0S and related tools.

Kapitan looks very promissing:

https://kapitan.dev/pages/blog/04/12/2022/kapitan-logo-5-years-of-kapitan/#why-do-i-need-kapitan

Actually I cannot understand, why it is not very popular while it could replace many tools or make them much better.

After integration we could see a Kapitan of k0smotron or even Commodore of k0smotron :)

@jnummelin jnummelin added the question Further information is requested label Aug 5, 2024
@jnummelin
Copy link
Member

Please let me know, is it a good idea to try to integrate your k0smotron with Commodore which is cloud-native SCM partialy based on Kapitan?

Unfortunately we've not used Commodore at all, so it's impossible to say whether it's a good idea or not. 😄

What problem would it solve for the end user?

In general, we're always happy to see k0smotron and k0s getting integrated into other cloud native tooling. So maybe try it out and see how it goes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants