Installation, updates & backup
Commissioning the appliance
Import the OVA, set network and time on the console, initialise K3s and open the Manager.
In EasyUC: VM console → Administration → Manage K3s → Initialize K3s (first node)
What it is for
EasyUC is delivered as a virtual appliance (OVA). The VM runs Linux with a text menu. In this menu you set network and time and run Initialize K3s once. This creates the Kubernetes cluster (K3s) with storage, the management of the database, search and messaging services, and the EasyUC Manager.
Initialisation runs without internet access. The container images are already inside the appliance. You install the EasyUC application itself afterwards in the Manager, see the chapter "Installing EasyUC and selecting modules".
The current OVA EasyUC-Appliance-Manager-2.0.11-ESXi.ova contains EasyUC Manager 2.0.11 but no EasyUC application yet. Download the OVA in the customer portal under Downloads (see "Customer portal: access and downloads") and, after this chapter, install EasyUC 4.9.49 in the Manager via EasyUC-Update → Erstinstallation.
Prerequisites
- VMware ESXi. The OVA is imported with "Create a VM from an OVF or OVA file"; you choose the port group during import.
- The OVA creates the VM with 8 vCPU, 16 GB RAM and a 160 GB disk, preferably on SSD. Do not reduce these values. For clusters and larger installations, agree the sizing with EasyUC.
- A fixed IP address, netmask, gateway and at least one DNS server.
- An internal NTP time source that the VM reaches on UDP 123. Periodic time synchronisation of VMware Tools must be switched off.
- Access to the VM console of the hypervisor. You log in with the console user of the appliance; you receive the credentials with the delivery.
- The OVA file from the customer portal, checked by SHA-256 checksum after downloading (see "Customer portal: access and downloads").
Step by step: import the OVA and set the network
Step by step: set the time source
Step by step: initialise K3s and open the Manager
Step by step: change the IP address later (single node only)
Fields and options
| Field / action | Meaning and use |
|---|---|
| Show IP Configuration / Show Routing table | Shows addresses and routes of the VM. |
| Configure interfaces | Activate or deactivate the network interface and set it by DHCP (Automatic (DHCP)) or statically (Manual). |
| NTP Server | Internal time sources for systemd-timesyncd. Public fallback time servers are disabled. Activation is only allowed with one node or exactly three nodes in the cluster. |
| Change passwords | Change the password of a console user (at least 5 characters). |
| Internet Access | Direct connection or HTTP Proxy with Proxy IP, Proxy Port and optional authentication. |
| Ping test | Check whether a host is reachable. |
| Increase disk size | Extend the file system after the VM disk has been enlarged. |
| Manage K3s | Before initialisation: Initialize K3s (first node), Prepare this node for joining (further node of a cluster, paired via Knoten hinzufügen in the Manager) and Pairing status. Afterwards: K3s Status, Change K3s IP (single node only), Set EasyUC owner password, Cluster SSH key and Uninstall K3s. |
| Set EasyUC owner password | Sets a random 24-character password for the owner account of the admin interface and shows it once. EasyUC has no default password. |
| Uninstall K3s | Removes K3s with all cluster data. The image store of the appliance is kept. |
| Reboot machine | Restarts the VM. K3s and EasyUC start automatically afterwards. |
Check the result and troubleshoot
- K3s Status shows the node in state
Ready. Pods that are not running can be deleted there to restart them. - The Manager page Übersicht shows the Knoten card with the new node and its load.
- "No valid IP address detected. Please configure the network interface first before installing K3s.": set up the interface first.
- "K3s installed but not ready after 10 minutes.": check time, disk and network; the following window shows the last K3s log lines. Then open K3s Status again.
- "EasyUC cluster is already initialized. Use 'Change K3s IP' if you need to reconfigure.": the appliance is already initialised.
- "ACTIVATION BLOCKED. No service was restarted." in the NTP menu: a check has failed. The entry can be saved as a pending configuration; it does not become active by itself, not even after a restart.
- "Multiple nodes detected in the cluster": changing the IP address through the menu is blocked in clusters with several nodes.