Standalone Installation

Overview

This documents will show you how to install KubeVela in standalone mode. There are two options:

  1. Local machine: Install on a local machine based on Linux, macOS or Windows operating system.
  2. Remote Linux server: Install on a remote Linux server with accessible IP address.

Standalone - 图1tip

Install KubeVela on a remote server with non-linux operating system is not fully tested.

About VelaD

We’ll use VelaD to install KubeVela in standalone mode. VelaD is a CLI tool that packages KubeVela with all dependencies for minimal installation and VelaUX. VelaD enables you to run KubeVela on any of docker compatible environments or Linux system.

  • VelaD leverages K3s and k3d to manage Kubernetes automatically. Users needn’t care the details about Kubernetes.
  • KubeVela along with all related images, and vela command line are packaged together that enables air-gapped installation of KubeVela and VelaUX.

Standalone - 图2caution

Installation with standalone mode is suited for development and testing purpose best that you don’t even aware of the Kubernetes inside. If you want to use it in production, you need to understand and maintain the K3s for Kubernetes management well.

Install in a local machine

1. Prepare environment

VelaD support installing KubeVela on machines based on these OS: Linux, macOS, Windows.

Requirements

  1. If you are using Linux or macOS, make sure your machine have curl installed.
  2. If you are using macOS or Windows, make sure you’ve already installed Docker.

2. Install VelaD and Setup KubeVela

Download VelaD

It will download and place the binary in your system PATH,

  • Linux/macOS
  • Windows

You may be required for root privilege during the installation process if not using root. If you don’t need the automation with root access, you can download from the release page and uncompress manually.

  1. curl -fsSl https://static.kubevela.net/script/install-velad.sh | bash -s v1.5.8

Check velad installed in /usr/local/bin/

Run following command in powershell with administrator privilege.

  1. powershell -Command "iwr -useb https://static.kubevela.net/script/install-velad.ps1 | iex"

Check velad installed in C:\vela\

Standalone - 图3info

VelaD helps install Vela CLI, which requires administrator privilege.

Start powershell as administrator

  1. Click on the ‘Start’ button to open the Start menu.
  2. Scroll to the Windows PowerShell shortcut folder then, right click on the Windows Powershell option and select ‘Run as administrator’.

Setup KubeVela

  1. velad install

expected output

  1. Preparing K3s images...
  2. Successfully prepare k3s image: /Users/sunjianbo/.vela/velad/k3s/k3s-airgap-images-amd64.tgz
  3. Successfully prepare k3d images
  5. ...snip...
  7. KubeVela control plane has been successfully set up on your cluster.
  8. If you want to enable dashboard, please run "vela addon enable /Users/sunjianbo/.vela/addons/velaux"
  10. Keep the token below if you want to restart the control plane
  11. K1075e7f6c77555e6ebdaf4854e4a2f39ae4287cfad23f27cdac5b33608d44633fe::server:zSpzbdbGzVxOwfBvvjgT
  13. 🚀 Successfully install KubeVela control plane
  14. 🔭 See available commands with `vela help`

Verify Installation

Export kubeconfig and list all built-in ComponentDefinition:

  • Linux/macOS
  • Windows
  1. export KUBECONFIG=$(velad kubeconfig --host)
  2. vela comp
  1. $env:PATH += ";$HOME\.vela\bin;"
  2. $env:KUBECONFIG = $(velad kubeconfig --host)
  3. vela comp

Standalone - 图4tip

  • When executing velad install, vela CLI (vela) is already installed and add to PATH automatically. So you can use it directly.
  • A file uesd to configure access to clusters is called kubeconfig file :::

expected output

  1. NAME                    DEFINITION                  DESCRIPTION
  2. config-helm-repository  autodetects.core.oam.dev    Config information to authenticate helm chart repository
  3. daemon                  daemonsets.apps             Describes daemonset services in Kubernetes.
  4. cron-task               cronjobs.batch              Describes cron jobs that run code or a script to completion.
  5. worker                  deployments.apps            Describes long-running, scalable, containerized services
  6. that running at backend. They do NOT have network endpoint
  7. to receive external network traffic.
  8. task                    jobs.batch                  Describes jobs that run code or a script to completion.
  9. webservice              deployments.apps            Describes long-running, scalable, containerized services
  10. that have a stable network endpoint to receive external
  11. network traffic from customers.
  12. config-image-registry   autodetects.core.oam.dev    Config information to authenticate image registry
  13. k8s-objects             autodetects.core.oam.dev    K8s-objects allow users to specify raw K8s objects in
  14. properties
  15. raw                     autodetects.core.oam.dev    Raw allow users to specify raw K8s object in properties.
  16. This definition is DEPRECATED, please use 'k8s-objects'
  17. instead.
  18. ref-objects             autodetects.core.oam.dev    Ref-objects allow users to specify ref objects to use.
  19. Notice that this component type have special handle logic.
  20. ``` Export kubeconfig and list all built-in ComponentDefinition:
  22. ### 3\. Install VelaUX
  24. VelaUX is a dashboard for KubeVela. It is a web application that runs in your cluster. You can access it with your browser. This is optional if you don't use UI console of KubeVela.
  26. -   Linux/macOS
  27. -   Windows

vela addon enable ~/.vela/addons/velaux

vela addon enable $HOME.vela\addons\velaux

  2. expected output

Addon: velaux enabled Successfully.

  2. By default, velaux don't have any exposed port, you can view it by:

vela port-forward addon-velaux -n vela-system 8080:80

  2. Choose `> local | velaux | velaux` for visit.
  4. For more VelaUX options, refer to [VelaUX addon]($e06854eba73d3440.md) document for other advanced installation arguments. :::
  6. VelaUX needs authentication. The default username is `admin` and the password is **`VelaUX12345`**.
  8. It requires you to override with a new password for the first login, please make sure to remember the new password.
  10. ### 4\. Cleanup
  12. This command will clean up KubeVela controllers along with the Kubernetes cluster, refer to [the advanced guide]($4b602c78f033b67f.md#uninstall) for more detailed steps.

velad uninstall

  2. ## Install on a remote Linux server
  4. This documents show you how to install KubeVela on a remote Linux server (e.g. aws EC2 or aliyun ECS) in standalone mode.
  6. ### 1\. Prepare a machine
  8. Prepare a Linux server, make sure it meets the following requirements:
  10. **Requirements**
  12. 1.  Make sure your machine have `curl` installed.
  13. 2.  This server has a public IP, or you can access the server's IP if it's a on-premise server.
  14. 3.  If you are using a cloud server, make sure you have opened the port 6443 in secure group.
  16. ### 2\. Install VelaD and Setup KubeVela
  18. #### Download VelaD
  20. Following script will download and place the binary in your system `PATH`, so you may be required for root privilege during the installation process. If you don't need the automation with root access, you can download from the [release page](https://github.com/kubevela/velad/releases) and uncompress manually.

curl -fsSl https://static.kubevela.net/script/install-velad.sh | bash

  2. Check `velad` installed in `/usr/local/bin/`
  4. #### Setup KubeVela
  6. Run the following command and replace the `$SERVER_PUBLIC_IP` with your server's public IP.

velad install —bind-ip=$SERVER_PUBLIC_IP

  2. expected output

Preparing K3s images… Successfully prepare k3s image: /Users/sunjianbo/.vela/velad/k3s/k3s-airgap-images-amd64.tgz Successfully prepare k3d images

…snip…

KubeVela control plane has been successfully set up on your cluster. If you want to enable dashboard, please run “vela addon enable /Users/sunjianbo/.vela/addons/velaux”

Keep the token below if you want to restart the control plane K1075e7f6c77555e6ebdaf4854e4a2f39ae4287cfad23f27cdac5b33608d44633fe::server:zSpzbdbGzVxOwfBvvjgT

🚀 Successfully install KubeVela control plane 🔭 See available commands with vela help 🔑 To access the cluster, set KUBECONFIG: export KUBECONFIG=$(velad kubeconfig —name default —host)

  2. #### Verify Installation
  4. Export kubeconfig and list all built-in ComponentDefinition:

export KUBECONFIG=$(velad kubeconfig —host) vela comp

  2. ![](/projects/kubevela-1.5-en/b6e7496f798247817562e4fe41b7d070.svg)tip
  4. -   When executing `velad install`, vela CLI (`vela`) is already installed and add to `PATH` automatically. So you can use it directly. Later we will access KubeVela on local machine, we will install vela CLI on local machine again.
  5. -   A file uesd to configure access to clusters is called *kubeconfig file*. Vela CLI also use this file to access KubeVela. :::
  7. expected output

NAME DEFINITION DESCRIPTION config-helm-repository autodetects.core.oam.dev Config information to authenticate helm chart repository daemon daemonsets.apps Describes daemonset services in Kubernetes. cron-task cronjobs.batch Describes cron jobs that run code or a script to completion. worker deployments.apps Describes long-running, scalable, containerized services that running at backend. They do NOT have network endpoint to receive external network traffic. task jobs.batch Describes jobs that run code or a script to completion. webservice deployments.apps Describes long-running, scalable, containerized services that have a stable network endpoint to receive external network traffic from customers. config-image-registry autodetects.core.oam.dev Config information to authenticate image registry k8s-objects autodetects.core.oam.dev K8s-objects allow users to specify raw K8s objects in properties raw autodetects.core.oam.dev Raw allow users to specify raw K8s object in properties. This definition is DEPRECATED, please use ‘k8s-objects’ instead. ref-objects autodetects.core.oam.dev Ref-objects allow users to specify ref objects to use. Notice that this component type have special handle logic.

  2. ### 3\. Install VelaUX
  4. VelaUX is a dashboard for KubeVela. It is a web application that runs in your cluster. You can access it with your browser.
  6. Run this command on remote server.

vela addon enable ~/.vela/addons/velaux serviceType=NodePort

  2. expected output

Addon: velaux enabled Successfully. … I0907 12:03:11.462606 98769 utils.go:156] find cluster gateway service vela-system/kubevela-cluster-gateway-service:9443 Please access addon-velaux from the following endpoints: +————-+—————-+———————————————-+——————————————+———-+ | CLUSTER | COMPONENT | REF(KIND/NAMESPACE/NAME) | ENDPOINT | INNER | +————-+—————-+———————————————-+——————————————+———-+ | local | apiserver | Service/vela-system/apiserver | apiserver.vela-system:8000 | true | | local | velaux | Service/vela-system/velaux | http://47.252.17.47:30000 | false | +————-+—————-+———————————————-+——————————————+———-+

  2. By adding `serviceType=NodePort`, we are telling VelaUX to expose service with K8s [NodePort](https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport) type. Check the endpoint of VelaUX with following command:

vela status addon-velaux -n vela-system —endpoint

  2. It will show URL like `http://PUBLIC-IP:PORT` access that URL with your browser.
  4. If you are using a cloud server, please open this port in secure group. :::
  6. ![](/projects/kubevela-1.5-en/adadd309cd63e4cc81476cb1404c35c9.svg)note
  8. For more VelaUX options, refer to [VelaUX addon]($e06854eba73d3440.md) document for other advanced installation arguments.
  10. VelaUX needs authentication. The default username is `admin` and the password is **`VelaUX12345`**.
  12. It requires you to override with a new password for the first login, please make sure to remember the new password.
  14. ### 4\. Access cluster From Local (Optional)
  16. You can access KubeVela with your local machine. Make sure you add `--bind-ip` when executing `velad install` command in the last step on the server.
  18. #### Copy KubeConfig
  20. Following command will print the kubeconfig for your cluster. `--external` means printed kubeconfig can be used from other machine (like your local machine).

cat $(velad kubeconfig —external)

  2. Then you need to copy this kubeconfig to your local machine. Let's say you saving a file in `~/.kube/velad-config` in your local machine.
  4. #### Install Vela CLI in Local
  6. To access the cluster, you also need to install `vela` CLI in your local machine.

curl -fsSl https://static.kubevela.net/script/install.sh | bash

  2. #### Access KubeVela
  4. Export KUBECONFIG environment variable and list all built-in ComponentDefinition:

export KUBECONFIG=~/.kube/velad-config vela comp

  2. ### 5\. Cleanup
  4. Run following command on remote server.
  6. This command will clean up KubeVela controllers along with the Kubernetes cluster, refer to [the advanced guide]($4b602c78f033b67f.md#uninstall) for more detailed steps.

velad uninstall ```