Install with Token and Fleetcommand CLI

Note	You can still install Domino if you don’t have the Fleetcommand Command Line Interface (CLI) or an installation token. Follow the steps in the Installation.

Use the Fleetcommand CLI to install Domino if you have an installation token from your Solutions Architect.

Installation with the Fleetcommand CLI is similar to the steps in the Installation. However, you don’t need quay.io credentials, and you don’t need to install fleetcommand-agent, Helm, or Docker. Instead, to authenticate, you use an installation token from your Solutions Architect. To issue installation commands, use the Fleetcommand CLI. To learn more about the telemetry being sent back to Domino, see Deployments Telemetry.

Prerequisites

To follow these instructions, you must have:

Fleetcommand CLI installed. You can download the binary from the following links:
- Linux version.
- Mac version.
- Windows version.
An installation token from your Domino Solutions Architect.

You must install Domino from a workstation with the following:

Access to the Kubernetes API.

If you have kubectl installed, kubectl access to the cluster where you’ll deploy Domino.
Acess to quay.io (you don’t need credentials).
Access to Docker images for Domino components.
Access to Helm charts.
Access to Fleetcommand, hosted at update.domino.tech.

Installation process

Important

A Domino install can’t be hosted on the subdomain of another Domino install. For example, if you have Domino deployed at data-science.example.com, you can’t deploy another instance of Domino at acme.data-science.example.com.

Connect to a workstation that meets the installation requirements listed previously. You don’t have to use an account with root privileges to run the installer.
Generate an installation token:
```
fctl register cluster --name <domino-deployment>
```
Update name from domino-deployment to something that identifies the purpose of your installation and contains the name of your organization. This command outputs a human-readable token that can be used later in the process to install Domino (step 6).
To generate a template configuration file named domino.yml, initialize the installer:
```
fctl init --version <domino-version-number>
```
Edit the configuration file with details about the target cluster, storage systems, and host domain. See the configuration reference for more information about available keys.
If you have custom install requirements, perform a dry installation run before you complete installation. A dry run outputs the full configuration without altering the cluster.
To install Domino, run the following code from the same directory as the configuration file.
```
fctl install --token <installation-token>
```
Installation can take up to 30 minutes to complete. The installer will output verbose logs and surface errors.

Upon successful installation, the terminal outputs the following:
```
<timestamp> INFO - fleetcommand_agent.Application - Deployment complete.
Domino is accessible at $YOUR_FQDN
```

You can access the application through HTTPS if you configure DNS for your fully-qualified domain name (FQDN) to point to an Ingress load balancer with the appropriate SSL certificates. The load balancer forwards traffic to your platform nodes.

Enable user registration

Use Keycloak to enable user registration, so users can access your fresh Domino install. Keycloak is a user authentication service that runs on a pod in your cluster.