Dedicated Tenancy Deployment Guide¶
This guide configures dedicated VMs for a Compose-based plan, then shows the additional settings for dedicated networks and Kubernetes clusters. These are isolation levels within Dedicated Tenancy, not separate tenancy types. For account-level isolation, use the BYOC deployment model.
Before You Begin¶
- Prepare your application's Compose specification for dedicated VMs.
- Choose Hosted SaaS or BYOC and onboard the appropriate provider and customer accounts.
- Decide whether the required boundary is a VM, network, Kubernetes cluster, or cloud account. Dedicated VMs alone do not dedicate all of these resources.
- Account for the cost and provisioning time of the chosen isolation level before setting plan prices and customer expectations.
Configure Dedicated Tenancy¶
Dedicated VMs¶
Set OMNISTRATE_DEDICATED_TENANCY and configure your provider account with hostedDeployment. Each deployment receives dedicated VMs and attached storage. The Kubernetes host cluster, network, and cloud account can remain shared.
This AWS example illustrates provider-account configuration; see the deployment schema for other cloud account fields. Replace the placeholders and merge this block into your application Compose specification:
x-omnistrate-service-plan:
name: 'Dedicated-Tenancy SaaS'
tenancyType: 'OMNISTRATE_DEDICATED_TENANCY'
deployment:
hostedDeployment:
awsAccountId: '<AWS_ACCOUNT_ID>'
awsBootstrapRoleAccountArn: 'arn:aws:iam::<AWS_ACCOUNT_ID>:role/omnistrate-bootstrap-role'
Dedicated Network¶
For customer-specific networks in Hosted SaaS, add CUSTOM_NETWORKS under the same plan's features:
Customers must choose or create a customer network when creating a deployment. Deployments using the same customer network can share its network and host cluster, so use separate networks when separate boundaries are required. The cloud account remains provider-owned. Configure private connectivity and routing as needed; see Customer Networks.
Choose this feature before creating the plan; it cannot be changed after the plan is created. For an existing network in a customer-owned account, use BYO-VPC, not the Hosted SaaS CUSTOM_NETWORKS feature.
Dedicated Kubernetes Cluster¶
For a dedicated Kubernetes host cluster per deployment, add the placement feature under the plan:
x-omnistrate-service-plan:
tenancyType: 'OMNISTRATE_DEDICATED_TENANCY'
features:
CUSTOM_DEPLOYMENT_CELL_PLACEMENT:
maximumDeploymentsPerCell: 1
Here, a deployment cell means the Kubernetes host cluster used for placement. This setting adds a cluster boundary to dedicated VMs; deployment-cell placement is distinct from infrastructure multi-tenancy and in-app multi-tenancy.
Configure this feature when the service has no existing deployments. It is not compatible with multi-tenant offerings or Serverless. Dedicated clusters increase cost and initial provisioning time; review Custom Deployment Cell Placement for the complete behavior and limitations. This setting does not create a dedicated cloud account.
Dedicated Account with BYOC¶
For dedicated-account isolation, offer BYOC and onboard a separate customer-owned account for each required account boundary. BYOC uses customer-supplied accounts; deployments in the same account share that account boundary. See BYOC account onboarding for setup guidance.