Skip to content

Commit 99396af

Browse files
committed
Rewritten, added illustrations for lifecycle showcase
Signed-off-by: Marina <[email protected]>
1 parent 1a89baa commit 99396af

File tree

4 files changed

+12
-31
lines changed

4 files changed

+12
-31
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,3 @@
11
node_modules
22
.docusaurus
3+
.DS_Store
Lines changed: 11 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,41 +1,21 @@
11
# Cluster API
22

3-
Kubernetes as a Service (KaaS) is a cloud service model that simplifies the deployment,
4-
management and scaling of Kubernetes clusters. By abstracting the underlying infrastructure,
5-
KaaS allows organisations to focus on developing and deploying applications without the
6-
complexities of cluster management. One of the most powerful tools for implementing KaaS
7-
is the Cluster API, an official Kubernetes project that provides declarative APIs and tools
8-
for managing the lifecycle of Kubernetes clusters.
3+
Cluster API is a Kubernetes project to manage and bootstrap Kubernetes clusters. It provides declarative APIs and tools for managing the Kubernetes cluster lifecycle. Cluster API is an implementation of *Kubernetes as a Service* (KaaS), a cloud service model that simplifies the deployment, management and scaling of Kubernetes clusters.
94

10-
Key benefits of Cluster API include:
5+
## Key benefits of Cluster API
6+
* **Standardization**: The provisioning of clusters is simplified through the use of YAML manifests. The declarative approach makes it easier to create, update, and delete clusters, thus automating version control and configuration of Kubernetes clusters.
7+
* **Abstraction**: Cluster API easily abstracts the underlying platform specific requirements like security, networking, and storage. The deployment across various environments, including public clouds (AWS, Azure, GCP), private clouds (OpenStack), and on-premises data centers, gets unified.
8+
* **Lifecycle Management:** Assuring a consistent workflow, Cluster API helps with provisioning, scaling, upgrading, and deletion of Kubernetes clusters. This consistency reduces operational overhead and automates repetitive workflows.
9+
* **Customization**: The extension and customization of Kubernetes clusters always yields the same experience across different infrastructures. Through the use of custom resource definitions (CRDs) and controllers, organizations can tailor the API to meet specific requirements, such as integrating with existing CI/CD pipelines or adding custom operational logic.
10+
* **Efficiency:** With Cluster API, organizations can automate repetitive tasks, reduce human error, and ensure that clusters are configured according to best practices. This automation leads to increased operational efficiency and faster delivery of applications - significantly reducing time-to-market (TTM).
1111

12-
* Declarative Cluster Management: Cluster API allows users to define the desired state of
13-
clusters using YAML manifests. This declarative approach simplifies the process of creating,
14-
updating, and deleting clusters, making it easier to automate and version control cluster
15-
configurations.
16-
* Infrastructure Abstraction: Cluster API abstracts the underlying infrastructure, enabling
17-
the deployment of Kubernetes clusters across various environments, including public clouds
18-
(AWS, Azure, GCP), private clouds (OpenStack), and on-premises data centers. This abstraction
19-
ensures that the same API can be used regardless of the infrastructure provider.
20-
* Consistent Lifecycle Management: Cluster API standardizes the lifecycle management of
21-
Kubernetes clusters, including provisioning, scaling, upgrading, and deletion. This consistency
22-
reduces operational overhead and ensures that clusters are managed uniformly across different
23-
environments.
24-
* Extensibility and Customization: Cluster API’s modular architecture allows for extensibility
25-
through the use of custom resource definitions (CRDs) and controllers. Organizations can tailor
26-
the API to meet specific requirements, such as integrating with existing CI/CD pipelines or
27-
adding custom operational logic.
28-
* Improved Operational Efficiency: By leveraging Cluster API, organizations can automate repetitive
29-
tasks, reduce human error, and ensure that clusters are configured according to best practices.
30-
This automation leads to increased operational efficiency and faster delivery of applications.
31-
32-
By using Kubernetes as a Service with Cluster API, organisations can achieve a highly automated,
33-
scalable and consistent approach to managing Kubernetes clusters across different environments.
34-
This allows them to focus more on application development, and less on the operational
35-
complexities of managing Kubernetes infrastructure.
12+
By using Kubernetes as a Service with Cluster API, organizations can achieve a highly automated, scalable and consistent approach to managing Kubernetes clusters across different environments. This allows them to focus more on application development, and less on the operational complexities of managing Kubernetes infrastructure.
3613

3714
## Lifecycle Management of Cluster API in OSISM
15+
Cluster API is a powerful tool, integrated in other services it can be seamlessly combined, and workload can be further abstracted and automated.
3816

3917
### Cluster API with OpenStack Magnum
18+
![In an OpenStack enviroment, a Magnum Plugin takes YAML-manifests to define and deploy specifications for Kubernetes clusters. First, Cluster Resources get defined. After that, Control Plane Nodes and Worker Nodes are configurated. If there are changes to the YAML-Manifests, Magnum will adjust the Nodes accordingly.](./images/cluster-api-magnum.png)
4019

4120
### Cluster API with SCS Cluster Stacks
21+
![SCS works in an different cloud infrastructure enviroments. SCS takes YAML-manifests to define and deploy specifications for Kubernetes clusters. First, Cluster Resources get defined. After that, Control Plane Nodes and Worker Nodes are configured. If there are changes to the YAML-Manifests, SCS will adjust the Nodes accordingly.](./images/cluster-api-scs.png)
Loading
Loading

0 commit comments

Comments
 (0)