Getting started

Before deployment

Prepare the following:

1. A supported Kubernetes cluster and dedicated namespace. trinetra-system is recommended.
2. The cloud projects or accounts approved for discovery and validation.
3. Customer-controlled object storage for reports and evidence, with versioning and retention matching customer policy.
4. Dedicated workload identities or service accounts for Trinetra components.
5. Read-only permissions for discovery and only the mutation permissions needed for explicitly approved tests.
6. An initial administrator email address.
7. A Trinetra entitlement from LNP Technologies. Deployment can be completed before activation when the selected distribution supports it.

Do not reuse personal credentials or place private keys in installation values.

For the Google Cloud Marketplace distribution, follow Google Cloud Marketplace BYOL and review every Marketplace deployment parameter. For a directly scoped engagement, see Assisted service.

Deploy the Kubernetes application

Use the installation path supplied for the selected Trinetra distribution. For Helm-based deployment, review Command-line deployment. Keep the user interface private by default and expose it only through customer-approved HTTPS, identity, and network controls.

Verify the installation

Confirm that:

• the controller, UI, and probe workloads are Ready;
• the UI opens through the approved access path;
• the initial administrator can sign in and changes any temporary password;
• the selected evidence store is writable by the controller;
• the intended cloud scope is selected;
• the Licence panel shows the expected installation ID and entitlement state; and
• discovery completes without an identity, permission, or API warning.

Activate and enrol scope

1. Open Licence in the Trinetra header.
2. Copy the Installation ID when LNP Technologies requests it for entitlement issuance.
3. Enter the activation key and select Activate.
4. Confirm the term, features, expiry, and limits.
5. Enrol only the cloud projects and Kubernetes clusters authorized for validation.
6. Confirm the home cluster used for Kubernetes execution.

Projects and clusters can consume permanent entitlement slots. Check the selection before enrolment.

Run a first safe validation

1. Open DR Testing.
2. Select the resource category and enrolled cloud scope.
3. Choose a non-production target.
4. Select Assessment mode.
5. Enable Dry run and review every preflight result.
6. Run without Dry run only after confirming target identity, capacity, authorization, rollback responsibility, and the change window.
7. Open History and verify the run, measurements, evidence object, and digest.

Dry runs and requests rejected during preflight do not consume a validation execution.