Verify the installed Appliance

Complete these checks after Management reports Verified success for the appliance. Use the Management administrator account and the network plan from installation.

Retain Access before leaving Installation

  1. Download the installation artifact bundle and wait for Checksum verified.

  2. Store the verified copy outside Management with restricted access. Record the appliance identity, version, installation date, node identities and Kubernetes API endpoint alongside it.

  3. Keep the matching release bundle and Talos boot artifact available for recovery preparation.

The artifact bundle contains administrative access material. Keep your recovery copy outside Management, which holds its copy in memory. A backup bundle has a different purpose and cannot replace the installation artifact bundle.

Verify Installation and initialize ERS

  1. Confirm that Management reports the appliance version selected during installation and a connected appliance. Review any health or capacity findings before continuing.

  2. Confirm that all intended nodes appear with the planned names and addresses.

  3. Verify DNS and reachability from the operator network for Management and the planned application hostname. Check the intended certificates at the endpoints you access.

  4. Follow Initialize ERS. Complete its application and PKI checks before treating ERS as ready for use.

  5. Open the configured application endpoint and verify the expected sign-in and product access using the identities established during ERS setup. Use the documentation for the bundled MTG product version for application-specific acceptance tests.

The version check alone cannot confirm that ERS is ready. Complete initialization and test your application configuration and integrations before handover.

Establish Operational Ownership

  1. Set up backups and external retention, and record who holds the complete recovery set.

  2. Make sure the responsible administrators can locate the retained artifact bundle and the reconnection procedure.

  3. Record the network, DNS, certificate and hypervisor owners needed for maintenance or recovery.

  4. Review Release notes and Recovery options with the operators who will maintain this deployment.

If a check fails, record the affected component and the error you see, retain the available diagnostics, and use Troubleshooting. Do not reinstall a verified appliance solely because Management has disconnected; use the reconnection procedure first.