Supported Configurations
This page applies to customers using automated cloud provisioning. If you bring your own Kubernetes cluster, refer to the Pre-Deployment Checklist for cluster requirements.
Summary
When using automated cloud provisioning, you select from supported regions, cluster sizing tiers, and Kubernetes versions. This page documents the available options and helps you choose the right configuration for your workload.
Why It Exists
Automated provisioning offers predefined sizing tiers rather than exposing raw cloud infrastructure parameters. This simplifies the provisioning request and ensures that the resulting cluster meets Keymate platform requirements without manual capacity planning.
How It Works
Cloud Provider Support
| Provider | Status | Notes |
|---|---|---|
| Azure | Available | AKS-based provisioning |
| AWS | Planned | EKS-based provisioning on the roadmap |
Region Selection
You specify the cloud region where the cluster and its supporting infrastructure will be created. Available regions depend on the cloud provider. The provisioning system creates all resources in the selected region for data residency compliance.
Cluster Sizing Tiers
Sizing tiers provide predefined compute capacity. Choose based on your expected workload.
| Tier | Intended workload | Node count | Use case |
|---|---|---|---|
| X-Small | Development and testing | 1 node | Individual developer environments, CI testing |
| Small | Small production or staging | 2 nodes | Low-traffic environments, staging validation |
| Medium | Standard production | 3 nodes | Typical production workloads |
| Large | High-traffic production | 5 nodes | High-throughput environments, large Tenant counts |
| X-Large | Enterprise scale | 7 nodes | Mission-critical deployments, high availability requirements |
Sizing tiers define the initial cluster capacity. Scale the cluster after provisioning through your cloud provider's management tools.
Kubernetes Version Support
The provisioning system supports current and recent Kubernetes versions. Specify your desired version in the cluster definition.
Recommendation: Use the latest stable version supported by your cloud provider unless your organization has specific version requirements.
Boundaries
- Sizing tiers define initial capacity — post-provisioning scaling is managed through standard cloud provider tools
- Region availability depends on the cloud provider
- Custom node types beyond the predefined tiers require manual cluster management
Example Scenario
Scenario
A platform engineer provisions a medium-sized production cluster in the West Europe region for a new Tenant.
Input
- Region: West Europe
- Sizing tier: Medium (3 nodes)
- Environment: Production
Expected Outcome
- The provisioning system creates a 3-node Kubernetes cluster in West Europe
- The system configures networking, DNS, and public IP automatically
- The cluster is ready for Keymate platform installation