fleetcommand-agent command reference

Note	See Run Commands to access the default entry point for the `fleetcommand-agent` container and launch commands.

fleetcommand-agent is an automation tool that deploys and configures Domino. It supports the following commands.

init

Generates a template configuration file.

Arguments

--file or -f: Write the template to the listed file system path. This must be a host volume mounted to the container.
--full or -F: Include optional and advanced portions of the template. Only use when advanced options are required. Configurations with these arguments are more complex to maintain.
--image-registry: Provide a registry URI to prepend to Domino images. This sets up the template for installation from a private Docker registry. Must be used with --full.
--version: Generate a configuration template for the listed Domino version.

Example

docker run --rm -v $(pwd):/install quay.io/domino/fleetcommand-agent:v32
init --file /install/domino.yml

run

Install Domino into a cluster specified by a Kubernetes configuration from the KUBECONFIG environment variable. You must pass a valid configuration file to this command.

Note

This fleetcommand-agent command requires mapping a Kubernetes configuration file into the container or running from inside the Kubernetes cluster with an appropriate service account. Configuration files that rely on third-party utilities (such as awscli for EKS) may not work. See the Install process section for details on installing from within the cluster.

Arguments

--file or -f: File system path to a complete and valid configuration file.
--kubeconfig: Path to a Kubernetes configuration file that contains the cluster and authentication information to use.
--dry: Run the command without making any permanent changes to the target cluster. This outputs all chart changes in the form of a list of newly added charts and a diff for any updated existing charts. Note that the --dry option relies on the Kubernetes secret, credential-store-domino-platform in the domino-system namespace. If any changes have been made to the secrets' schema, use the --local-secrets option along with --dry. This generates temporary secrets and avoids errors. You cannot use this option on a completely fresh Kubernetes cluster onto which Domino has not yet been installed.
--services or -s: Specific services to operate on. Multiple services can be specified in comma-delimited format: -s "service-a,service-b"

Example

docker run --rm -v $(pwd):/install quay.io/domino/fleetcommand-agent:v32 run --file /install/domino.yml

destroy

Remove all resources from the target cluster for a configuration file.

Note

Arguments

--file or -f: File system path to a complete and valid configuration file.
--kubeconfig: Path to Kubernetes configuration file that contains the cluster and authentication information to use.
--dry: Run the command without making permanent changes to the target cluster. A dry run checks service account permissions and generates detailed logs about the charts deployed with the configuration.

Example

docker run --rm -v $(pwd):/install quay.io/domino/fleetcommand-agent:v32
destroy --file /install/domino.yml