Deployment & Infra

This guide is for infrastructure and platform engineers evaluating or operating MicroStax.

Recommended Starting Topology

• MicroStax API as the control plane
• dashboard as the operator UI
• Postgres for metadata
• k3s or Kubernetes as the environment execution target
• object storage for snapshot artifacts when snapshot workflows are enabled
• ingress for API and dashboard exposure

Runtime Targets

Target	When to use it
k3s	Lightweight local, lab, or MVP deployments
GKE	Managed Google Cloud deployment
EKS	Managed AWS deployment
AKS	Managed Azure deployment

What Platform Teams Need To Operate

• cluster access for namespace, service, ingress, and policy management
• persistent metadata storage
• ingress and DNS strategy
• environment cleanup and idle policies
• audit and governance visibility
• storage strategy for snapshots and restore jobs

Practical Rollout Sequence

1. stand up the API, dashboard, Postgres, and ingress
2. validate environment creation with isolated Blueprints
3. introduce templates and basic team usage
4. promote a shared baseline for one service group
5. move developers to overlays
6. layer on snapshots, seeds, and mirrored validation
7. enable governance and audit review processes

Operational Concerns

Capacity

Watch:

• total active namespaces
• replica growth from stateful or exposed services
• snapshot storage consumption
• overlay TTL compliance

Security

Ensure:

• org scoping is configured correctly
• ingress is limited to required services
• share links are handled intentionally
• snapshot sanitization policies are reviewed

Observability

Use:

• logs and traces for environment debugging
• metrics for fleet health and routing visibility
• audit and compliance views for governance-sensitive workflows

Reference Material

• cluster deployment examples exist under docs/cluster/deploy-microstax.md
• cloud deployment guidance exists under docs/infra/gcp-guide.md