Skip to content

Customer networks

Customer networks is an advanced Deployment Model feature that allows your Customers to define network partitioning on a dedicated stack, while keeping the service Deployed in the Service Provider Account. This allows complete isolation, provisioning a dedicated stack that is not shared with other Customers, that gives the ability to setup a private network path for your customer to connect with the service, while keeping the option of making the service provisioned self served.

Note

This feature is available for Service Provider Deployment Model only. BYOC Deployment Model always provides isolation by provisioning the services in the customer account directly. The model is not supported for Omnistrate Hosted Deployment Model.

Enabling Customer Networks

Customer Provided Networks can only be disabled (default) or enabled. When enabled, your Customers will have to choose or create a new Custom Network whenever creating a new instance. Instances created with the same Custom Network will be co-located on same Deployment Cell and will share the same network interface.

A Customer Network is an abstract concept that defines a CIDR range for a specific Cloud Provider and a Region. Because each such network is owned by certain customer, instances belonging to different Customers within the Plan are never co-located on Deployment Cells with instances from other Customers.

Warning

Enabling this feature can potentially increase your infrastructure cost significantly as it can result in additional Kubernetes Host Clusters being provisioned, one for each Customer defined Custom Network. Consider this when defining the Pricing for your Plans.

Customer Provided Networks can be enabled when creating new Plan by adding following lines to your compose spec file:

x-omnistrate-service-plan:
  features:
    CUSTOM_NETWORKS:

or the following lines on the service spec file:

features:
  CUSTOM_NETWORKS:

This feature cannot be modified once Plan is created.

Configuring Private Networking

For each Custom Network created it is possible to configure private network connectivity to allow Customers to use the services with private networking.

A way to define private networking is using VPC peering. For more details on how to configure VPC peering you can referent to the VPC peering guideline.

Check other options for Private networking in the Private networking guideline