Deployment Center/Operations

Day-two operations

Update and operate X2 safely

Storage-node updates are consensus workflows. KMS maintenance is an independent operator procedure. Use immutable manifests, preserve quorum, and verify convergence after every change.

Command platform

Linux

Updates

Use the correct workflow for each component

Rolling X2 Node update

  1. Publish a signed immutable release.
  2. Open Control → Updates.
  3. Submit the URL ending in /releases/<version>/manifest.json.
  4. Review platform, digest, signature, and node order.
  5. Monitor drain, restart, catch-up, and convergence.

Never submit latest.json as an update target.

X2 KMS maintenance

Update one member at a time. Preserve quorum, encrypted storage, TLS identities, client-key grants, and unseal custody. Every restarted member returns sealed and must be unsealed locally.

XC update

Verify and replace the client binary, then run xc --version. User aliases remain outside cluster consensus.

Release evidence

Record the immutable manifest URL, parent revision, UI revision, signatures, node order, and post-update convergence result.

Health and logs

Start with readiness, then inspect the node

Linux

systemctl status x2-node
journalctl -u x2-node --since today
curl --fail https://x2.example.com/health/ready

Windows

Get-Service X2Node
Get-Content 'C:\ProgramData\X2\logs\x2-node-service.log' -Tail 100
Invoke-WebRequest https://x2.example.com/health/ready

macOS

sudo launchctl print system/com.edgedrive.x2-node
tail -n 100 /usr/local/var/log/x2/x2-node.stderr.log
curl --fail https://x2.example.com/health/ready

Reference

Network, paths, and security boundaries

Default ports

8443/TCP
Public HTTPS, console, S3, API, MCP
9443/TCP
Inter-node mTLS mesh
18200/TCP
X2 KMS HTTPS API
18201/TCP
X2 KMS Raft traffic

Persistent paths

Linux
/etc/x2, /var/lib/x2, /var/log/x2
Windows
C:\ProgramData\X2
macOS
/usr/local/etc/x2, /usr/local/var/lib/x2

Security boundaries

  • KMS root token and shares remain with KMS operators.
  • Enrollment tokens are single-use and short-lived.
  • Private keys remain node-local.
  • Normal startup never erases storage.

Troubleshooting

Common deployment questions

Can several nodes run on one development machine?

Yes. Give each process unique public and internal ports plus distinct state, log, metadata, and disk paths.

Can the bootstrap password change on restart?

No. Bootstrap credentials are consumed only when the administrator is first created. Change existing credentials through IAM.

What happens when KMI is disabled?

X2 remains functional, but credential envelopes and object data are stored without provider-backed encryption.

Can a legacy multi-service cluster upgrade in place?

No. The unified architecture requires a destructive clean-cluster migration with no state import or mixed-version runtime.

Where is node.yaml documented?

x2-node configure generates the restart snapshot from CLI or environment values. Operators normally do not maintain a large YAML manually.

Where do I add another node?

Follow the dedicated cluster expansion guide; do not bootstrap another independent cluster.