Domino is a Kubernetes native platform. You can install it on many different kinds of infrastructure. It’s deployed and configured with a tool called fleetcommand-agent.
- Requirements
-
Review the requirements to install Domino.
- Installation overview
-
Install Domino and review the installation process, regardless of platform.
- Install with Token and Fleetcommand Command Line Interface (CLI)
-
Install Domino with Fleetcommand’s CLI if you have an installation token from your Solutions Architect.
- Amazon Web Services (AWS) deployments
-
Install Domino on Amazon Elastic Kubernetes Service (EKS).
- Azure deployments
-
Install Domino on Azure Kubernetes Service (AKS).
- Google Cloud Platform (GCP) deployments
-
Install Domino on Google Kubernetes Engine (GKE).
- Private or offline installation
-
Install Domino without a connection to the Internet.
- VMware Tanzu deployments
-
Install Domino on VMware vSphere with Tanzu.
- fleetcommand-agent Install Tool
-
The primary tool to install, configure, and upgrade Domino.
- Upgrade Domino
-
Upgrade your Domino install.
- Dataset upgrade prior to 4.5
-
Review improvements to Datasets in Domino 4.5+.
- Set up custom certificates
-
Configure Domino to connect to private services.
- User acceptance testing
-
Verify that Domino features work as expected.
- Troubleshoot installation
-
Test for, and fix common installation pitfalls.
- Fleetcommand Command Line Interface (CLI) reference
-
Reference information about commands and arguments for the Fleetcommand CLI.
- Streamlined domino.yaml downloads
-
Download pre-configured
domino.yamlfiles to ease installation. - Fleetcommand CLI reference
-
Use Fleetcommand CLI to install Domino.