Trust Center Installation Overview¶

Deployment Modes¶

The current release of the Anyware Trust Center uses a single-node installation into a K3S cluster using a provided script. The installation script creates and configures the node for you, and does not require manual setup.

Future releases of the Anyware Trust Center will support multi-node environments, installed into a Kubernetes cluster which you create and manage yourself.

When to Use Single-Node Deployments¶

The single-node instance of the Anyware Trust Center is appropriate for the following use cases:

• You do not require high availability or redundancy; your security policies permit delayed policy enforcement in the event your Anyware Trust Center is down or unavailable for any reason.

• You are deploying a proof-of-concept system for testing purposes.

• You do not have in-house Kubernetes expertise, and are not retaining our Professional Services team.

• You do not expect to grow beyond the initial node.

  Note: Migrating from single-node to multi-node deployments

  When multi-node deployments are available, a migration procedure will be published to support moving from one model to the other.

Failure Ramifications in Single-Node Deployments¶

The single-node deployment of the Anyware Trust Center is not a high-availability configuration. If the Anyware Trust Center is unavailable for any reason, including network connectivity issues, the following will occur until service is restored:

• Endpoints cannot be managed and policies cannot be enforced.

• New endpoints cannot be added.

• Monitoring and logging of endpoints will be paused.

• Users can still connect to remote sessions while the Anyware Trust Center is down.

Trusted Zero Clients continue to accumulate logging data even if the Anyware Trust Center is offline. When the Anyware Trust Center is reachable again, logging data will catch up automatically, without loss in continuity.

Planning for Future Multi-Node Deployments¶

If any of the following describe your use case, you should plan to use the Multi-Node Installation method when it is available:

• You require high-availability SLAs and real-time monitoring of endpoints (in a single-node deployment, if the Anyware Trust Center is unreachable, monitoring is unavailable until the connection is restored).

• You have enterprise requirements such as multiple Trust Centers deployed in different regions, or a mix of cloud and on-premesis deployments.

• You will create or extend your own self-managed Kubernetes cluster, either by yourself or in consultation with our Professional Services team.