Skip to content

Commit dc51ce6

Browse files
committed
docs: refactoring README.md
Signed-off-by: Dario Tranchitella <[email protected]>
1 parent 6123d9a commit dc51ce6

File tree

1 file changed

+123
-19
lines changed

1 file changed

+123
-19
lines changed

README.md

+123-19
Original file line numberDiff line numberDiff line change
@@ -3,45 +3,149 @@
33
<p align="left">
44
<img src="https://img.shields.io/github/license/clastix/kamaji"/>
55
<img src="https://img.shields.io/github/go-mod/go-version/clastix/kamaji"/>
6-
<a href="https://github.com/clastix/kamaji/releases">
7-
<img src="https://img.shields.io/github/v/release/clastix/kamaji"/>
8-
<img src="https://goreportcard.com/badge/github.com/clastix/kamaji">
9-
</a>
6+
<a href="https://github.com/clastix/kamaji/releases"><img src="https://img.shields.io/github/v/release/clastix/kamaji"/></a>
7+
<img src="https://goreportcard.com/badge/github.com/clastix/kamaji">
8+
<a href="https://kubernetes.slack.com/archives/C03GLTTMWNN"><img alt="#kamaji on Kubernetes Slack" src="https://img.shields.io/badge/slack-@kubernetes/kamaji-blue.svg?logo=slack"/></a>
109
</p>
1110

1211
![Logo](assets/logo-black.png#gh-light-mode-only)
1312
![Logo](assets/logo-white.png#gh-dark-mode-only)
1413

15-
**Kamaji** is a **Kubernetes Control Plane Manager**. It operates Kubernetes at scale with a fraction of the operational burden. Kamaji is special because the Control Plane components are running inside pods instead of dedicated machines. This solution makes running multiple Control Planes cheaper and easier to deploy and operate.
14+
### 🤔 What is Kamaji?
1615

17-
<img src="docs/content/images/architecture.png" width="600">
16+
**Kamaji** is a **Kubernetes Control Plane Manager** leveraging on the concept of [**Hosted Control Plane**](https://clastix.io/post/the-raise-of-hosted-control-plane-in-kubernetes/).
1817

19-
## Main Features
18+
Kamaji's approach is based on running the Kubernetes Control Plane components in Pods instead of dedicated machines.
19+
This allows operating Kubernetes clusters at scale, with a fraction of the operational burden.
20+
Thanks to this approach, running multiple Control Planes can be cheaper and easier to deploy and operate.
2021

21-
- **Multi-cluster Management:** centrally manage multiple Kubernetes clusters from a single Management Cluster.
22+
_Kamaji is like a fleet of Site Reliability Engineers with expertise codified into its logic, working 24/7 to keep up and running your Control Planes._
23+
24+
<img src="docs/content/images/architecture.png" width="600" style="display: block; margin: 0 auto">
25+
26+
### 📖 How it works
27+
28+
Kamaji is extending the Kubernetes API capabilities thanks to [Custom Resource Definitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#customresourcedefinitions).
29+
30+
By installing Kamaji, two pairs of new APIs will be available:
31+
32+
- `TenantControlPlane`, the instance definition of your desired Kubernetes Control Plane
33+
- `Datastore`, the backing store used by one (or more) `TenantControlPlane`
34+
35+
The `TenantControlPlane` (short-named as `tcp`) objects are Namespace-scoped and allows configuring every aspect of your desired Control Plane.
36+
Besides the Kubernetes configuration values, you can specify the Pod options such as limit, request, tolerations, node selector, etc.,
37+
as well as how these should be exposed (e.g.: using a `ClusterIP`, a `LoadBalancer`, or a `NodePort`).
38+
39+
The `TenantControlPlane` is the stateless definition of the Control Plane allowing to set up the required components for a full-fledged Kubernetest cluster.
40+
The state is managed by the `Datastore` API, a cluster-scoped resource which can hold the data of one or more Kubernetes clusters.
41+
42+
> For further information about the API specifications and all the available options,
43+
> refer to the official [API reference](https://kamaji.clastix.io/reference/api/#tenantcontrolplane).
44+
45+
### ⭐️ Main features
46+
47+
- **Fast provisioning time**: depending on the infrastructure, Tenant Control Planes are up and ready to serve traffic in **16 seconds**.
48+
- **Streamlined update**: the rollout to a new Kubernetes version for a given Tenant Control Plane takes just **10 seconds**, with a Blue/Green deployment to avoid serving mixed Kubernetes versions.
49+
- **Resource optimization**: thanks to the Datastore decoupling, there's no need of odd number instances (e.g.: RAFT consensus) by allowing to save up to 60% of HW resources.
50+
- **Scale from zero to the moon**: scale down the instance when there's no usage, or automatically scale to support the traffic spikes reusing the Kubernetes patterns.
51+
- **Declarative approach, constant reconciliation**: thanks to the Operator pattern, drift detection happens in real-time, maintaining the desired state.
52+
- **Automated certificates management**: Kamaji leverages on `kubeadm` and the certificates are automatically created and rotated for you.
53+
- **Managing core addons**: Kamaji allows configuring automatically `kube-proxy`, `CoreDNS`, and `konnectivity`, with automatic remediation in case of user errors (e.g.: deleting the `CoreDNS` deployment).
54+
- **Auto Healing**: the `TenantControlPlane` objects in the management cluster are tracked by Kamaji, in case of deletion of those, everything is created in an idempotent way.
55+
- **Datastore multi-tenancy**: optionally, Kamaji allows running multiple Control Planes on the same _Datastore_ instance leveraging on the multi-tenancy of each driver, decreasing operations and optimizing costs.
56+
- **Overcoming `etcd` limitations**: optionally, Kamaji allows using a different _Datastore_ thanks to [`kine`](https://github.com/k3s-io/kine) by supporting `MySQL` or `PostgreSQL` as an alternative.
57+
- **Simplifying mixed-networks setup**: thanks to [`Konnectivity`](https://kubernetes.io/docs/tasks/extend-kubernetes/setup-konnectivity/),
58+
the Tenant Control Plane is connected to the worker nodes hosted in a different network, overcoming the no-NAT availability when dealing with nodes with a non routable IP address
59+
(e.g.: worker nodes in a different infrastructure).
60+
61+
### 🚀 Use cases
62+
63+
- [**Creating a private Managed Kubernetes Service**](https://clastix.io/post/netsons-builds-a-managed-kubernetes-service-with-kamaji-and-open-stack/)
64+
- [**Building a Platform as a Service**](https://aenix.io/cozystack/)
65+
- [**Overcoming public Managed Kubernetes Services**](https://clastix.io/post/overcoming-eks-limitations-with-kamaji-on-aws/) such as EKS
66+
- [**Hybrid infrastructures**](https://clastix.io/post/bridging-the-gap-hybrid-kubernetes-clusters-with-remote-control-planes/):
67+
host the Control Plane on the Cloud and worker nodes on prem or vice-versa, according to your needs.
68+
- [**Kubernetes at the edge**](https://clastix.io/post/edgevolution-unleashing-the-power-of-kubernetes-clusters-for-a-revolutionary-edge-computing-experience/):
69+
take full advantage of the _Kubernetes API Server as a service_ paradigm.
70+
- **Kubernetes Control Plane as a Service:** centrally manage multiple Kubernetes clusters from a single management point (_Multi-Cluster management_).
2271
- **High-density Control Plane:** place multiple control planes on the same infrastructure, instead of having dedicated machines for each control plane.
2372
- **Strong Multi-tenancy:** leave users to access the control plane with admin permissions while keeping them isolated at the infrastructure level.
2473
- **Kubernetes Inception:** use Kubernetes to manage Kubernetes with automation, high-availability, fault tolerance, and autoscaling out of the box.
25-
- **Bring Your Own Device:** keep the control plane isolated from data plane. Worker nodes can join and run consistently everywhere: cloud, edge, and data-center.
74+
- **Bring Your Own Device:** keep the control plane isolated from data plane. Worker nodes can join and run consistently from everywhere: cloud, edge, and data-center.
2675
- **Full CNCF compliant:** all clusters are built with upstream Kubernetes binaries, resulting in full CNCF compliant Kubernetes clusters.
2776

28-
## Roadmap
77+
> 🤔 You'd like to do the same but don't know how?
78+
> 💡 [CLASTIX](https://clastix.io/) can help you with your needs!
79+
80+
### 🍦 Vanilla Kubernetes clusters
81+
82+
Kamaji is **not** yet-another-Kubernetes distribution: you have full freedom on the technology stack to provide to end users.
83+
Kamaji is a perfect fit for Platform Engineering, hiding the complexity of the Control Plane management to developers and DevOps engineers.
84+
85+
The provided Kubernetes Control Planes are [CNCF compliant clusters](https://kamaji.clastix.io/reference/conformance/).
86+
87+
<img src="https://raw.githubusercontent.com/cncf/artwork/master/projects/kubernetes/certified-kubernetes/versionless/color/certified-kubernetes-color.png" style="display: block; width: 75px; margin: 0 auto">
88+
89+
### 🐢 Cluster API support
90+
91+
Kamaji is **not** a [Cluster API](https://cluster-api.sigs.k8s.io/) replacement, rather, it plays very well with it.
92+
93+
Since Kamaji is just focusing on the Control Plane a [Kamaji's Cluster API Control Plane provider](https://github.com/clastix/cluster-api-control-plane-provider-kamaji) has been developed.
94+
95+
### 🛣️ Roadmap
2996

3097
- [x] Dynamic address on Load Balancer
3198
- [x] Zero Downtime Tenant Control Plane upgrade
32-
- [x] Join worker nodes from anywhere
33-
- [x] Alternative datastore MySQL and PostgreSQL
34-
- [x] Pool of multiple datastores
35-
- [x] Seamless migration between datastores
99+
- [x] [Join worker nodes from anywhere thanks to Konnectivity](https://kamaji.clastix.io/concepts/#konnectivity)
100+
- [x] [Alternative datastore MySQL and PostgreSQL](https://kamaji.clastix.io/guides/alternative-datastore/)
101+
- [x] [Pool of multiple datastores](https://kamaji.clastix.io/concepts/#datastores)
102+
- [x] [Seamless migration between datastores](https://kamaji.clastix.io/guides/datastore-migration/)
36103
- [ ] Automatic assignment to a datastore
37104
- [ ] Autoscaling of Tenant Control Plane
38-
- [x] Provisioning through Cluster APIs
105+
- [x] [Provisioning through Cluster APIs](https://github.com/clastix/cluster-api-control-plane-provider-kamaji)
39106
- [ ] Terraform provider
40107
- [ ] Custom Prometheus metrics
41108

109+
### 🎥 Multimedia
110+
111+
- YouTube ▶️ [Hands-on introduction to Kamaji](https://www.youtube.com/watch?v=HhevxwQWQ88)
112+
- YouTube ▶️ [Scaling Kubernetes up to 1,000 Control Planes](https://www.youtube.com/watch?v=W_HXRXJh96U)
113+
- YouTube ▶️ [Equinix, Kamaji, and Cluster API](https://www.youtube.com/watch?v=TLBTqROj_wA)
114+
- YouTube ▶️ [Rancher & Kamaji: solving multitenancy challenges in the Kubernetes world](https://www.youtube.com/watch?v=VXHNrMmlF8U)
115+
- YouTube ▶️ [Enabling Self-Service Kubernetes clusters with Kamaji and Paralus](https://www.youtube.com/watch?v=JWA2LwZazM0)
116+
117+
### 🏷️ Versioning
118+
119+
Versioning adheres to the [Semantic Versioning](http://semver.org/) principles.
120+
A full list of the available releases is available in the GitHub repository's [**Release** section](https://github.com/clastix/kamaji/releases).
121+
122+
### 📄 Documentation
123+
124+
Further documentation can be found on the official [Kamaji documentation website](https://kamaji.clastix.io/).
125+
126+
### 🤝 Contributions
127+
128+
Contributions are highly appreciated and very welcomed!
129+
130+
In case of bugs, please, check if the issue has been already opened by checking the [GitHub Issues](https://github.com/clastix/kamaji/issues) section.
131+
In case it isn't, you can open a new one: a detailed report will help us to replicate it, assess it, and work on a fix.
132+
133+
You can express your intention in working on the fix on your own.
134+
The commit messages are checked according to the described [semantics](https://github.com/projectcapsule/capsule/blob/main/CONTRIBUTING.md#semantics).
135+
Commits are used to generate the changelog, and their author will be referenced in it.
136+
137+
In case of **✨ Feature Requests** please use the [Discussion's Feature Request section](https://github.com/clastix/kamaji/discussions/categories/feature-requests).
138+
139+
### 📝 License
140+
141+
The Kamaji Cluster API Control Plane provider is licensed under Apache 2.0.
142+
The code is provided as-is with no warranties.
143+
144+
### 🛟 Commercial Support
145+
146+
![CLASTIX](https://avatars.githubusercontent.com/u/39170129?s=50&v=4) [CLASTIX](https://clastix.io/) is the commercial company behind Kamaji and the Cluster API Control Plane provider.
42147

43-
## Documentation
44-
Please, check the project's [documentation](https://kamaji.clastix.io/) for getting started with Kamaji.
148+
If you're looking to run Kamaji in production and would like to learn more, **CLASTIX** can help by offering [Open Source support plans](https://clastix.io/support),
149+
as well as providing a comprehensive Enterprise Platform named [CLASTIX Enterprise Platform](https://clastix.cloud/), built on top of the Kamaji and [Capsule](https://capsule.clastix.io/) project (now donated to CNCF as a Sandbox project).
45150

46-
## Contributions
47-
Kamaji is Open Source with Apache 2 license and any contribution is welcome. Open an issue or suggest an enhancement on the GitHub [project's page](https://github.com/clastix/kamaji). Join the [Kubernetes Slack Workspace](https://slack.k8s.io/) and the [`#kamaji`](https://kubernetes.slack.com/archives/C03GLTTMWNN) channel to meet end-users and contributors.
151+
Feel free to get in touch with the provided [Contact form](https://clastix.io/contact).

0 commit comments

Comments
 (0)