Tillered Arctic

cluster

Cluster operations

cluster

Manage cluster operations.

Synopsis

arctic cluster <subcommand> [flags]

Subcommands

SubcommandDescription
initInitialize cluster
identityShow cluster identity
syncTrigger synchronization
statusShow gossip status for diagnostics

init

Initialize a cluster for legacy upgraded agents.

Usage

arctic cluster init [--force]

Flags

FlagDescription
--forceForce reinitialize even if cluster exists

Required Scope

urn:tillered:arctic:admin

Example

arctic cluster init

Output

Cluster initialized
Cluster ID:       01HABC...
Created By:       01HXYZ...
Oldest Peer:      01HXYZ...
Was Created:      true

Notes

  • Only needed for agents upgraded from older versions
  • New agents have clusters initialized during bootstrap
  • Use --force to regenerate the cluster ID (destroys existing cluster state)

identity

Show the cluster identity of a peer.

Usage

arctic cluster identity

Authentication

No authentication required (public endpoint).

Example

arctic cluster identity

Output

Peer ID:     peer_01KBYMHC35F0N070F3XXMEZAZR
Public Key:  qnGyPtol7lqzLYU3989eaC+K4xda0w9KXlcEOM9cSBQ=
License ID:  lic_01KB45EYP1VJ1RZEGJDPKJQ9V4
Cluster ID:  clu_01KBYMHMRJ92E090P50VRKG4ZC
Version:     v0.1.0

JSON Output

Use -j as shorthand for -o json:

arctic cluster identity -j
{
  "peer_id": "peer_01KBYMHC35F0N070F3XXMEZAZR",
  "public_key": "qnGyPtol7lqzLYU3989eaC+K4xda0w9KXlcEOM9cSBQ=",
  "license_id": "lic_01KB45EYP1VJ1RZEGJDPKJQ9V4",
  "cluster_id": "clu_01KBYMHMRJ92E090P50VRKG4ZC",
  "version": "v0.1.0"
}

Use Cases

  • Verify peer identity before adding
  • Check license ID matches your cluster
  • Retrieve public key for verification

sync

Trigger cluster synchronization.

Usage

arctic cluster sync

Required Scope

urn:tillered:arctic:admin

Example

arctic cluster sync

Output

Cluster sync triggered

Behavior

Triggers immediate:

  1. Gossip protocol heartbeats to all peers
  2. Configuration regeneration
  3. Subsystem processing (network, firewall, etc.)

Use Cases

  • Force configuration update after changes
  • Speed up propagation of new peers
  • Troubleshoot synchronization issues

status

Show gossip status for cluster diagnostics.

Usage

arctic cluster status

Required Scope

urn:tillered:arctic:admin

Example

arctic cluster status

Output

Gossip Status
-------------
Local Peer:        peer_01KBYMHC35F0N070F3XXMEZAZR
Cluster ID:        clu_01KBYMHMRJ92E090P50VRKG4ZC

Peer Status:
  peer_01KBYMD32Z2RVDE3G5Y9M530QR:
    Last Seen:     2025-12-09 10:15:30 UTC
    Status:        healthy
    Registry Hash: a1b2c3d4...

Registry:
  Services:        5
  Routes:          12
  Hash:            e5f6g7h8...

JSON Output

arctic cluster status -j

Use Cases

  • Diagnose cluster synchronization issues
  • Verify peer connectivity and health
  • Check registry hash for drift detection
  • Monitor gossip protocol state

See Also