From f00e177e8793ebad06ec4bac0ed1205a18300bb9 Mon Sep 17 00:00:00 2001 From: Julian Hennig Date: Thu, 3 Aug 2023 14:40:03 +0200 Subject: [PATCH] Update website content Signed-off-by: Julian Hennig --- README.md | 75 ++++++++++++++++++++++++++++++++++++++--------------- index.html | 76 ++++++++++++++++++++++++++---------------------------- 2 files changed, 90 insertions(+), 61 deletions(-) diff --git a/README.md b/README.md index 6f84a90..b40e4f2 100644 --- a/README.md +++ b/README.md @@ -1,48 +1,81 @@ -# k0smotron +# k0smotron - An open source control plane manager for unified cluster management -Experience unparalleled isolation, scalability, and resource efficiency for your Kubernetes control planes with k0smotron - the ultimate Kubernetes management solution. It's designed for k0s. +k0smotron allows you to unify your Kubernetes cluster management for an efficient use of resources. It’s designed for k0s. ## Features -### Kubernetes-in-Kubernetes +### Control Plane-as-a-Service -k0smotron allows you to easily create and manage the clusters in an existing Kubernetes cluster. This allows unparalled scalability and flexibility when you have to work with many clusters. It allows truly homogenous setup for all control planes and thus eases the maintenance burden. +k0smotron streamlines k0s control plane creation and management within your management cluster, reducing traditional operational overhead. k0smotron encapsulates the control plane service as a pods (and other Kubernetes constructs) and provides an intuitive approach to cluster lifecycle management through ClusterAPI integration. -### True control and worker plane separation +### Enhanced High Availability -Using k0smotron the clusters controlplane and workerplane are truly separated. The controlplane, running on an existing cluster has no direct networking connection to the workerplane. This is similar patter nhow all the major cloud providers separate the control and worker planes on the managed clusters. +k0smotron allows you to leverage the power of SQL databases as a data store for your control planes through Kine. This flexibility means you can choose from a variety of data storage operators like Postgres, MySQL, or your cloud provider's managed databases. This offers a robust, high-availability solution, eliminating the dependency on Etcd. -### Bring your own workers +### Bring Your Own Worker Nodes -With k0smotron you can connect worker nodes from ANY infrastructure to your cluster control plane. +k0smotron prioritizes flexibility in the integration of worker nodes and allows easy connection or creation of nodes. This ensures node isolation and flexible scaling, minimizing interference with the control plane. k0smotron operates with or without the ClusterAPI, offering you the freedom to select your preferred operational mode. ## How does it work -You install k0smotron operator into an existing Kubernetes cluster. k0smotron operator will create and manage k0s control planes in that cluster. It leverages the natural pattern of working with custom resources to manage the lifecycle of the k0s control planes. k0smotron will automatically create all the needed Kubernetes lower level constructs, such as pods, configmaps etc., to +The k0smotron controller manager is a service that will be installed into an existing Kubernetes cluster. k0smotron will create and manage k0s control planes in the management cluster like workloads. It leverages the natural pattern of working with custom resources to manage the lifecycle of the k0s control planes. k0smotron will automatically create all the needed Kubernetes lower level resources, such as pods, configmaps, etc. -k0smotron is an Kubernetes operator designed to manage the lifecycle of k0s control planes in a Kubernetes (any distro) cluster. By running the control plane on a k8s cluster we can enjoy and leverage the high availability and auto-healing functionalities of the underlying cluster, a.k.a Mothership. +k0smotron is a service designed to manage the lifecycle of k0s control planes in a Kubernetes (any distro) cluster. By running the control plane on a k8s cluster we can enjoy and leverage the high availability and auto-healing functionalities of the management cluster. -TODO: Insert pic +![k0smotron-diagram-v2](images/k0smotron-diagram-v2.png) ## Use cases -### CI/CD +### Development and CI/CD -Often when running integration and end-to-end testing for your software running in Kubernetes you need somewhat temporary clusters in CI. Why not leverage the true flexibility and create those clusters on-demand using k0smotron. Creating a controlplane is as easy as creating a custom resource, so is the deletion of it. No more long living snowflake clusters for CI purposes. +In the process of continuous integration and end-to-end testing, a temporary Kubernetes Cluster is needed. With k0smotron, these clusters can be created on demand in a declarative way and thus integrated into the existing CI process with ease. This avoids cluster sprawl and long-living snowflake clusters. -### Edge +### Edge Container Management -Running Kubernetes on the network edge usually means running in low resource infrastructure. What this often means is that setting up the controlplane is either a challenge or a mission impossible. Running the controlplane on a existing cluster, on a separate dedicated infrastructure, removes that challenge and let's you focus on the real edge. +Kubernetes at the edge typically comes with the requirement of a low resource footprint. As a result, clusters with distributed roles are more challenging and a lot of single-node clusters are created. Managing the large number of clusters confronts us with almost impossible tasks. -Running on the edge often also means large number of clusters to manage. Do you really want to dedicate nodes for each cluster controlplane and manage all the infrastructure for those? +Offloading the control plane means that the persistence layer of the cluster can run on dedicated hardware and workloads can be managed at the edge on devices dedicated to their purposes. With k0smotron worker nodes get ephemeral. -### Multi-cloud +### Multi-cloud Cluster LCM + +A multi-cloud strategy is essential these days. But managed Kubernetes offerings are often different in versioning or even the built-in tooling. + +With k0smotron, you can run the control plane management cluster in a public or private cloud provider of your choice and the worker nodes in different clouds. With this you have an approach to unified cluster management, providing one flavor on all clouds and saving the costs for the highly available Control Plane in the cloud. + +## Getting Started + +Getting started with k0smotron is easy. Simply install the controller into an existing cluster: + +``` bash +kubectl apply -f https://docs.k0smotron.io/stable/install.yaml +``` + +Then create a k0s control plane: +``` bash +kubectl apply -f - < - K0smotron + k0smotron @@ -41,13 +41,13 @@ wave-circle

Team Lens proudly presents

-

From pets to cattle: Streamline your Kubernetes control plane management with k0smotron

+

An open source control plane manager for unified cluster management

-

Experience unparalleled isolation, scalability, and resource efficiency for your Kubernetes control planes with k0smotron - the ultimate Kubernetes management solution. It’s designed for k0s

+

k0smotron allows you to unify your Kubernetes cluster management for an efficient use of resources. It’s designed for k0s

@@ -62,20 +62,20 @@

Features

-

Kubernetes-in-Kubernetes

-

k0smotron allows you to easily create and manage the clusters in an existing Kubernetes cluster. This allows unparalled scalability and flexibility when you have to work with many clusters. It allows a truly homogenous setup for all control planes and thus eases the maintenance burden.

+

Control Plane-as-a-Service

+

k0smotron streamlines k0s control plane creation and management within your management cluster, reducing traditional operational overhead. k0smotron encapsulates the control plane service as a pods (and other Kubernetes constructs) and provides an intuitive approach to cluster lifecycle management through ClusterAPI integration.

-

True control and worker plane separation

-

Using k0smotron the clusters controlplane and workerplane are truly separated. The controlplane, running on an existing cluster has no direct networking connection to the workerplane. This is a similar pattern to how all the major cloud providers separate the control and worker planes on the managed clusters.

+

Enhanced High Availability

+

k0smotron allows you to leverage the power of SQL databases as a data store for your control planes through Kine. This flexibility means you can choose from a variety of data storage operators like Postgres, MySQL, or your cloud provider's managed databases. This offers a robust, high-availability solution, eliminating the dependency on Etcd.

-

Bring your own workers

-

With k0smotron you can connect worker nodes from ANY infrastructure to your cluster control plane. This allows you to manage all control planes in a shared infrastructure, and in a homogenous way, but connect each cluster’s workers from separate remote infrastructures.

+

Bring Your Own Worker Nodes

+

k0smotron prioritizes flexibility in the integration of worker nodes and allows easy connection or creation of nodes. This ensures node isolation and flexible scaling, minimizing interference with the control plane. k0smotron operates with or without the ClusterAPI, offering you the freedom to select your preferred operational mode.

@@ -84,13 +84,15 @@

Bring your own workers

-
+

How does it work

-

You install k0smotron operator into an existing Kubernetes cluster. k0smotron operator will create and manage k0s control planes in that cluster. It leverages the natural pattern of working with custom resources to manage the lifecycle of the k0s control planes. k0smotron will automatically create all the needed Kubernetes lower level constructs, such as pods, configmaps etc., to

-

k0smotron is an Kubernetes operator designed to manage the lifecycle of k0s control planes in a Kubernetes (any distro) cluster. By running the control plane on a k8s cluster we can enjoy and leverage the high availability and auto-healing functionalities of the underlying cluster, a.k.a Mothership.

+

The k0smotron controller manager is a service that will be installed into an existing Kubernetes cluster. k0smotron will create and manage k0s control planes in the management cluster like workloads. It leverages the natural pattern of working with custom resources to manage the lifecycle of the k0s control planes. k0smotron will automatically create all the needed Kubernetes lower level resources, such as pods, configmaps, etc.

+

k0smotron is a service designed to manage the lifecycle of k0s control planes in a Kubernetes (any distro) cluster. By running the control plane on a k8s cluster we can enjoy and leverage the high availability and auto-healing functionalities of the management cluster.

-
- how-does-it-work-diagram +
+
+
+ how-does-it-work-diagram
@@ -105,21 +107,22 @@

Use cases

-

CI/CD

-

Often when running integration and end-to-end testing for your software running in Kubernetes you need somewhat temporary clusters in CI. Why not leverage the true flexibility and create those clusters on-demand using k0smotron. Creating a controlplane is as easy as creating a custom resource, so is the deletion of it. No more long living snowflake clusters for CI purposes.

+

Development and CI/CD

+

In the process of continuous integration and end-to-end testing, a temporary Kubernetes Cluster is needed. With k0smotron, these clusters can be created on demand in a declarative way and thus integrated into the existing CI process with ease. This avoids cluster sprawl and long-living snowflake clusters.

-

Edge

-

Running Kubernetes on the network edge usually means running in low resource infrastructure. What this often means is that setting up the controlplane is either a challenge or a mission impossible. Running the controlplane on an existing cluster, on a separate dedicated infrastructure, removes that challenge and lets you focus on the real edge.

-

Running on the edge often also means a large number of clusters to manage. Do you really want to dedicate nodes for each cluster controlplane and manage all the infrastructure for those?

+

Edge Container Management

+

Kubernetes at the edge typically comes with the requirement of a low resource footprint. As a result, clusters with distributed roles are more challenging and a lot of single-node clusters are created. Managing the large number of clusters confronts us with almost impossible tasks.

+

Offloading the control plane means that the persistence layer of the cluster can run on dedicated hardware and workloads can be managed at the edge on devices dedicated to their purposes. With k0smotron worker nodes get ephemeral.

-

Multi-cloud

-

With k0smotron you can run your control plane management cluster (a.k.a Mothership) in one cloud provider and the workloads in various other cloud providers. This allows you to build and maintain a very streamlined approach to multi cloud.

+

Multi-cloud Cluster LCM

+

A multi-cloud strategy is essential these days. But managed Kubernetes offerings are often different in versioning or even the built-in tooling.

+

With k0smotron, you can run the control plane management cluster in a public or private cloud provider of your choice and the worker nodes in different clouds. With this you have an approach to unified cluster management, providing one flavor on all clouds and saving the costs for the highly available Control Plane in the cloud.

@@ -130,7 +133,7 @@

Getting started

-

Getting started with k0smotron is easy. Simply install the controller into existing cluster:

+

Getting started with k0smotron is easy. Simply install the controller into an existing cluster:

 
 kubectl apply -f https://docs.k0smotron.io/stable/install.yaml
@@ -144,8 +147,9 @@ 

Getting started

metadata: name: my-k0smotron spec: {} -EOF
-

And that's it. You now have a k0s control plane running in your cluster. For further details how to work with the created cluster control plane check out the documentation.

+EOF + +

That's it. You now have a k0s control plane running in your cluster. For further details how to work with the new cluster control plane check out the documentation.

@@ -157,39 +161,31 @@

FAQ

- What is the relation of k0smotron with Cluster API + What is the relationship between k0smotron and Cluster API?
- While k0smotron currently is a "standalone" controller for k0s control planes we're looking to expand this as a full Cluster API provider. Or rather set of providers as were looking to implement both ControlPlane and Bootstrap providers. + k0smotron already provides integration into Cluster API, can create Control Planes and act as a CAPI Bootstrap Provider for Worker Nodes. We are looking to expand k0smotron as a full Cluster API provider.
- How is k0smotron different from typical multi-cluster management solutions such as Tanzu, Rancher etc.? + How is k0smotron different from multi-cluster management solutions such as Tanzu, Rancher, etc.?
- Most of the existing multi-cluster management solutions provision specific infrastructure for the control planes, in most cases VMs. In all of the cases we've looked at the worker plane infrastructure is also provisioned in the same infrastructure with the control plane and thus not allowing you to fully utilize the capabilities of the management cluster. + Most of the existing multi-cluster management solutions provision infrastructure for the control planes, in most cases VMs. In all of the cases we've looked at the worker plane infrastructure is also provisioned in the same infrastructure with the control plane and thus not allowing you to fully utilize the capabilities of the management cluster.
- What do we mean with pet vs. cattle? -
-
- As the controlplanes for clusters are pretty static, it means they are usually managed as "pets". Using an operator like k0smotron to manage k0s control planes within an existing Kubernetes cluster is a "cattle" approach that allows for a more scalable and flexible management of clusters. This approach makes it easier to maintain a consistent and homogeneous setup across all clusters, while also taking advantage of the high availability and auto-healing features of Kubernetes. -
-
-
-
- How is this different for managed Kubernetes providers? + How is this different to managed Kubernetes providers?
- Control and Flexibility: k0smotron gives you full control over your cluster configurations within your existing Kubernetes cluster, offering unparalleled flexibility.
+ Control and Flexibility: k0smotron gives you full control over your cluster configurations within your Management cluster, offering unparalleled flexibility.
Bring Your Own Workers: Unlike managed Kubernetes providers, k0smotron allows you to connect worker nodes from any infrastructure, providing greater freedom and compatibility.
Cost Efficiency: By leveraging your existing Kubernetes cluster, k0smotron helps reduce costs associated with managing separate clusters or paying for additional resources.
- Homogeneous Setup: k0smotron ensures a consistent configuration across clusters, simplifying maintenance and management tasks.
+ Homogeneous Setup: k0smotron ensures a consistent configuration across clouds, simplifying maintenance and management tasks.
@@ -213,4 +209,4 @@

Join the
k0smotron community

- + \ No newline at end of file