Connection and Application Settings

SSH Credentials

Buckit Manager uses SSH to install upgrades, swap systemd units, run rolling restarts, reboot hosts, and provision replacement nodes. Operations that run over SSH are unavailable until you configure SSH credentials for the cluster.

Reach the SSH credentials page from the Configure SSH credentials item in the cluster gear menu, or from the prompt shown when you start an SSH-based operation without credentials configured.

Configure a default credential set for the cluster:

• Authentication — choose how Buckit Manager authenticates:

  • Use SSH agent — authenticate through keys loaded into your ssh-agent (run ssh-add first).

  • Use key file — point Buckit Manager at a private key file on disk, with an optional passphrase.

  • Password — authenticate with an SSH password. Most production servers disable this; use it only for legacy hosts.

• SSH user and SSH port — the login user and port.

• Use sudo (passwordless) — required when the SSH user is not root. The user must be able to install packages, write configuration under /etc, prepare storage directories, and manage the systemd service.

The Hosts table lists every node in the cluster. You can set a per-host SSH port, enable custom credentials for individual hosts that differ from the default, and select Test SSH connection to probe every host and confirm reachability before saving.

Select Save SSH credentials on this computer for future operations to persist the credentials so later operations can reuse them without re-prompting. When saved, credentials and passphrases are encrypted at rest.

Admin Credentials

Buckit Manager uses admin API credentials to fetch detailed cluster and hardware facts and to run admin-API operations. Reach the admin credentials page from the Set admin credentials item in the cluster gear menu.

Provide:

• Admin API URL — the S3 endpoint Buckit Manager uses for admin calls.

• Root username and Current root password — the cluster root credentials.

• Skip TLS certificate verification — enable for deployments using a self-signed or otherwise untrusted certificate.

The stored password is encrypted and is never displayed back to you.

This page also includes a Danger zone for removing the cluster definition from the manager. Removing a cluster stops tracking it; the hosts and data are not changed.

History

The History section lists every action you have run from this manager, with the time, operation, cluster, scope (cluster-wide, a single host, or a set of hosts), status, and duration.

Read-only fetches and background polling are not recorded, and command-line invocations of bm are out of scope.

You can:

• Filter by status (Succeeded, Failed, Running, Canceled) and by cluster, and search by operation, cluster, or hostname.

• Select View on a finished entry to see its detailed result.

• Select Clear history to remove all entries from this machine. Clearing history does not affect any cluster.

Application Settings

The Settings section manages the Buckit Manager application itself.