Installation

Constella runs on a Kubernetes cluster. Awanio or a certified partner performs the installation. This page lists what the cluster needs, what gets installed, and the steps an administrator takes afterwards.

Requirements

Kubernetes cluster

Item	Requirement
Kubernetes	1.28 or later
Free capacity	4 vCPU and 8 GiB of memory. An empty installation uses about 1 vCPU and 3 GiB at rest; the rest is headroom for synchronization and monitoring as you add cloud accounts.
Storage	A StorageClass that provides ReadWriteOnce volumes, with about 60 GiB free: 20 GiB for the database, 20 GiB for images, 10 GiB for metrics, plus room to grow.
Node address	The IP address of a cluster node, which Constella's internal certificates are issued for. It must be an IP address, not a host name.
Image downloads	The first installation downloads about 3 GB of container images. On a slow or lossy link, allow 30 minutes or more.

Network access

• Users to Constella: HTTPS to the console address. For a public or company-wide address, put Constella behind the cluster's ingress controller with a TLS certificate.
• Constella to your clouds: the engine calls each connected platform's API directly, for example vCenter on port 443 or a public cloud's API endpoints. Where direct access is not possible, configure a proxy per cloud account (Multicloud › Proxy).

What gets installed

Everything goes into one namespace, constella by default:

Component	Purpose
Console	The web application users open in the browser
Engine services	Authentication, inventory and scheduling, image service, monitoring, notifications, web console for remote access, and the Kubernetes management service
MySQL	The inventory database, on a persistent volume
Metrics store	Time-series storage for monitoring data, on a persistent volume
Operator	Keeps the engine services deployed, upgraded and configured

After installation

1. Sign in and change the password

Sign in with the administrator account you received from the installer. Then open the account menu in the top-right corner and choose Change Password.

2. Set the published address

Constella needs to know the address users open in their browser, for example https://constella.example.com. It uses that address for the remote console of virtual machines, and warns users who open the console at any other address.

Run this against the cluster, replacing the address with yours:

kubectl -n constella exec deploy/constella-cloudpods-climc -- \
  /opt/yunion/bin/climc service-config \
  --config api_server=https://constella.example.com common

The change applies straight away. Users who saw the address warning should sign out and sign in again.

3. Connect your first cloud account

In System View, open Multicloud › Accounts and follow Cloud Accounts.

4. Check the feature modules

The installer enables the Container (Kubernetes), Load Balancing and bare-metal server modules, so their menus appear in System View right away.

If they are missing on an installation made before the installer did this, ask Awanio support to run the installer again. It only adds the missing modules and leaves the rest of the installation unchanged.

Checking the installation

All pods in the namespace should be Running and ready:

kubectl -n constella get pods

Symptom	What to do
Pods stay in ImagePullBackOff for a long time	The image download was interrupted. Kubernetes retries by itself; on lossy links this can take a while. Check that the nodes can reach the image registry.
The console shows "The configured Web console access address is …"	The published address does not match the address you opened. Set it as in step 2, or use the address shown.
A menu you expect is missing	Check the view switcher first (see The three views), then step 4 above.