Install a Kloudfuse POC
A Kloudfuse POC (proof of concept, a trial) runs on a small Kubernetes cluster in your cloud account: AWS, Google Cloud, or Azure. One script, install.sh, installs it in one of two ways:
| Install | What you provide | What install.sh does |
|---|---|---|
New cluster (Terraform) |
A cloud account you can sign in to |
Terraform creates the network, the cluster and its nodes, a storage bucket, and a static IP, then Kloudfuse is installed on it. |
Existing cluster (Helm) |
A cluster with a node for Kloudfuse, a storage bucket, and a static IP |
Installs Kloudfuse on it with Helm. No Terraform. |
For cloud requirements, settings, and upgrades, see POC Overview. For errors, see POC Troubleshooting.
Prerequisites
-
license.json, the license file Kloudfuse gave you. -
A DNS name for Kloudfuse, such as
kfuse.example.com, and access to its DNS. The install asks you to add anArecord for it. -
For an existing cluster: a kubeconfig context with
cluster-admin, and a node labelled and taintedkf_role=kfusewith at least 16 vCPU and 128 GiB. Existing cluster requirements lists everything. -
The required tools.
install.shchecks for them first.
Signed in to your cloud
| Cloud | Sign in with |
|---|---|
AWS |
|
Google Cloud |
|
Azure |
|
For an existing cluster, you can get its kubeconfig context by running…
-
aws eks update-kubeconfig --name <cluster>, -
gcloud container clusters get-credentials <cluster>, or -
az aks get-credentials --name <cluster> --resource-group <group>.
Installation
Create an empty folder and copy the license.json file to it. Open a terminal there and run:
curl -fsSLO https://install.kloudfuse.io/kfuse-poc/install.sh && bash install.sh
Then:
-
Choose install type:
1for a new cluster,2for a cluster you already have. -
New cluster: choose the cloud (
aws,gcp, orazure). Existing cluster: confirm your kubeconfig context with Enter, or type another one; the cloud is read from the cluster. -
install.shdownloads the matching bundle intokfuse-poc-<version>/kfuse-poc-<bundle>/and carries on from there. -
Answer the questions. Press Enter to take the value in
[brackets]. You choose the password of theadminlogin here: remember it, as the cluster keeps only its hash. -
New cluster: review Terraform’s plans and type
yes. -
Add the DNS record it prints (
<domain> A <static IP>), then press Enter. -
It installs Kloudfuse and waits until it answers. Then open
https://<domain>;and log in asadmin.
On a new cluster, the whole install, including creating the cloud resources, takes about 30 minutes. On an existing cluster, it takes about 10–15 minutes.
Post-install
Keep everything in the bundle folder. Run follow-up actions on the install from there:
| Action | Run, in the bundle folder |
|---|---|
Carry on after a stop, or reinstall |
|
Change a setting, or the admin password |
|
Add Helm values the install doesn’t set |
Put them in |
Remove Kloudfuse |
|
./uninstall.sh removes only the items that the install created.
|
The folder you started in also gets a copy of uninstall.sh, so ./uninstall.sh works from there too: it finds the install in the bundle folder and removes it.
Required Tools
install.sh checks them first and shows a table of what it found.
| Tool | Version |
|---|---|
Matching the cluster |
|
3.8 or later, or 4.x |
|
yq ( |
4.x |
|
any |
|
any |
|
any |
|
any |
|
any |
Terraform (new cluster only) |
1.5 or later (1.x) |
AWS CLI (new cluster on AWS) |
2.x |
|
current |
Azure CLI (new cluster on Azure) |
current |
On an existing cluster, the cloud’s CLI is needed only if your kubeconfig signs in with it.