Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.

Summary and goal

The dual deployment of selected Kessel components to HCC clusters is intended to be the first step in a full migration to a multi-cluster architecture. This will also enable the Kessel Inventory gRPC service to be exposed outside the current cluster (RHCLOUD-41403) . The specific services in scope are Relations, Inventory, SpiceDB, and the SpiceDB operator. There will be no cross-cluster traffic between the Kessel deployments, other than for communication with the shared PostgreSQL database

Acceptance Criteria 

• The Relations, Inventory, SpiceDB, and SpiceDB operator components are deployed and functionally equivalent in both the original and new HCC (hccs01ue1, hccp01ue1) clusters.
• There is no negative impact on the user experience or performance during the dual deployment.
• A single shared PostgreSQL database is used as the system of record to ensure consistency between the original and new clusters.
• As an operator, observability is enabled for all newly deployed components, with logs collected in CloudWatch and the same metrics as currently collected in the old CRC cluster collected by Prometheus.
• As an operator, Grafana dashboards and alerts are adjusted to include data from the new cluster.
• As an operator, the original deployment will continue to operate as it does today, serving as the immediate rollback strategy.
• The deployment of replication pipelines is not part of this Epic (but would need to be considered long-term for deprecating the existing cluster deployment).

Checklist

Open Questions