Feature Overview (aka. Goal Summary)  

The metadata for customer clusters provisioned in a particular cloud provider region should be stored in an XCM instance within the same region itself.

The goal here is to offer data residency and data sovereignty to managed OpenShift customers out of the box. Customers have varying requirements around data residency based on policies and/or compliance requirements. In order to capture these evolving requirements that differ by industry, region, country, and regulation, we want to bake the basic elements of data residency into the core architecture itself.

Requirements (aka. Acceptance Criteria):

• Each XCM instance needs to be fully contained to perform lifecycle operations on clusters provisioned within the cloud provider region.
• Each XCM instance needs to have its own database where the cluster spec and metadata will be stored
• Customers will interact with a particular XCM instance, installed in cloud provider region A, to manage their clusters within the cloud provider region A.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Out of Scope

• A single region in Singapore is in scope for this milestone.
• Telemetry, Identity, RH subscriptions, and analytics data will not be part of the scope of data residency in this milestone
   

  Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.