Deployment on Containers

The documented customer deployment uses a Windows installer and IIS. A supported container image, container installation procedure, and component-by-component Windows-only matrix have not yet been confirmed. This page is deployment planning guidance, not a tested container installation recipe.

Use the Windows installer workflow for the currently documented installation path.

• Rasterex Engine processes documents server-side. The current installation uses Windows/IIS; supported container images and Windows-only runtime requirements need confirmation.
• Rasterex Canvas is the embedded viewing and markup surface. The supplied deployment hosts it in IIS; alternative container hosting requires verification.
• Rasterex Backend is the Node.js annotation and database service. The Windows service installation does not establish whether its complete dependency set is supported in Linux or Windows containers.
• Customer database remains customer-owned. Plan persistent storage, backups, and connectivity separately from viewer containers.

For a confirmed Windows container image, schedule the workload on a compatible Windows node pool, such as an AKS Windows user node pool. Windows containers cannot run on Linux nodes. Match the image operating-system version to the supported host compatibility rules.

Before publishing manifests, confirm the Rasterex base image and tag, unattended installation and licensing, runtime dependencies, document and cache storage, network endpoints, health checks, and upgrade procedure.

See AKS Windows containers and Windows container version compatibility for platform requirements.

Base image: pending Rasterex confirmation. Container CPU, memory, and storage sizing: pending representative workload testing. Do not reuse installer host recommendations as container resource requests or limits.

Measure concurrent document processing, large DWG and IFC files, cache growth, and annotation traffic before selecting resource limits. Record the tested component versions, file sizes, concurrency, and recovery behavior with the final deployment configuration.