You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-12Lines changed: 15 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,11 @@
1
-
# HelmVM platform
1
+
# Embedded Cluster platform
2
2
3
-
This repository houses a cluster installation prototype that utilizes the k0s and k0sctl platforms. It showcases an alternative approach to deploying clusters and serves as a starting point for further exploration and advancement. In HelmVM, all components and functionalities are consolidated into a single binary, this binary facilitates a streamlined cluster installation process, removing the need for external dependencies (rpms, debs, etc). Remote hosts are managed using SSH.
3
+
This repository houses a cluster installation prototype that utilizes the k0s and k0sctl platforms.
4
+
It showcases an alternative approach to deploying clusters and serves as a starting point for further exploration and advancement.
5
+
In Embedded Cluster, all components and functionalities are consolidated into a single binary, this binary facilitates a streamlined cluster installation process, removing the need for external dependencies (rpms, debs, etc).
6
+
Remote hosts are managed using SSH.
4
7
5
-
HelmVM includes by default the Kots Admin Console and the OpenEBS Storage provisioner, you can very easily embed your own Helm Chart to the binary.
8
+
Embedded Cluster includes by default the Kots Admin Console and the OpenEBS Storage provisioner, you can very easily embed your own Helm Chart to the binary.
6
9
7
10
## Building and running
8
11
@@ -17,7 +20,7 @@ You can also build binaries for other architectures with the following targets:
17
20
18
21
## Single node deployment
19
22
20
-
To create a single node deployment you can upload the HelmVM binary to a Linux x86_64 machine and run:
23
+
To create a single node deployment you can upload the Embedded Cluster binary to a Linux x86_64 machine and run:
21
24
22
25
```
23
26
$ ./embedded-cluster install
@@ -35,7 +38,7 @@ In this case, it's not necessary to execute this command exclusively on a Linux
35
38
36
39
## Deploying Individual Nodes
37
40
38
-
HelmVM also facilitates deploying individual nodes through the use of tokens, deviating from the centralized approach.
41
+
Embedded Cluster also facilitates deploying individual nodes through the use of tokens, deviating from the centralized approach.
39
42
To follow this path, you need to exclude yourself from the centralized management facilitated via SSH.
40
43
41
44
### Installing a Multi-Node Setup using Token-Based Deployment
@@ -73,18 +76,18 @@ Copy the command provided and run it on the server you wish to join to the clust
For this to function, you must ensure that the HelmVM binary is present on all nodes within the cluster.
79
+
For this to function, you must ensure that the Embedded Cluster binary is present on all nodes within the cluster.
77
80
78
81
79
82
### Upgrading clusters
80
83
81
-
If your installation employs centralized management, simply download the newer version of HelmVM and execute:
84
+
If your installation employs centralized management, simply download the newer version of Embedded Cluster and execute:
82
85
83
86
```
84
87
$ embedded-cluster apply
85
88
```
86
89
87
-
For installations without centralized management, download HelmVM, upload it to each server in your cluster, and execute the following command as **root** on each server:
90
+
For installations without centralized management, download Embedded Cluster, upload it to each server in your cluster, and execute the following command as **root** on each server:
HelmVM allows you to embed your own Helm Charts so they are installed by default when the cluster is installed or updated. For sake of documenting this let's create a hypothetical scenario: you have a software called `rocks` that is packaged as a Helm Chart and is ready to be installed in any Kubernetes Cluster.
122
+
Embedded Cluster allows you to embed your own Helm Charts so they are installed by default when the cluster is installed or updated. For sake of documenting this let's create a hypothetical scenario: you have a software called `rocks` that is packaged as a Helm Chart and is ready to be installed in any Kubernetes Cluster.
120
123
121
-
Your Helm Chart is in a file called `rocks-1.0.0.tgz` and you already have a copy of HelmVM binary in your $PATH. To embed your Chart you can run:
124
+
Your Helm Chart is in a file called `rocks-1.0.0.tgz` and you already have a copy of mbedded Cluster binary in your $PATH. To embed your Chart you can run:
This command will create a binary called `rocks` in the current directory, this command is a copy of HelmVM binary with your Helm Chart embedded into it. You can then use the `rocks` binary to install a cluster that automatically deploys your `rocks-1.0.0.tgz` Helm Chart.
129
+
This command will create a binary called `rocks` in the current directory, this command is a copy of mbedded Cluster binary with your Helm Chart embedded into it. You can then use the `rocks` binary to install a cluster that automatically deploys your `rocks-1.0.0.tgz` Helm Chart.
127
130
128
131
If you want to provide a customised `values.yaml` during the Helm Chart installation you can also embed it into the binary. You can do that with the following command:
129
132
@@ -148,7 +151,7 @@ $ embedded-cluster embed \
148
151
149
152
## Miscellaneous
150
153
151
-
HelmVM stores its data under `$HOME/.embedded-cluster` directory, you may want to create a backup of the directory, specially the `$HOME/.embedded-cluster/etc` directory. Inside the `$HOME/.embedded-cluster/etc` directory you will find the `k0sctl.yaml` and the `kubeconfig` files, the first is used when installing or upgrading a cluster and the latter is used when accessing the cluster with `kubectl` (a copy of `kubectl` is also kept under `$HOME/.embedded-cluster/bin` directory and you may want to include it into your PATH).
154
+
mbedded Cluster stores its data under `$HOME/.embedded-cluster` directory, you may want to create a backup of the directory, specially the `$HOME/.embedded-cluster/etc` directory. Inside the `$HOME/.embedded-cluster/etc` directory you will find the `k0sctl.yaml` and the `kubeconfig` files, the first is used when installing or upgrading a cluster and the latter is used when accessing the cluster with `kubectl` (a copy of `kubectl` is also kept under `$HOME/.embedded-cluster/bin` directory and you may want to include it into your PATH).
152
155
153
156
If you want to use an already existing `k0sctl.yaml` configuration during the `install` command you can do so by using the `--config` flag.
0 commit comments