Goal

To align with the initiative of moving core HCC/Fabric workloads to a dedicated HCC cluster, Payload Tracker is to be deployed to the new HCC cluster while maintaining its presence on the CRC cluster. This dual deployment model ensures service availability during the migration of internal traffic.

Both deployments will utilize the same shared cloud resources (PostgreSQL) enabled by the multi-cluster network topology. The consumer and vacuum components will be fully migrated to HCC cluster (i.e. scaled down completely on CRC). The API component will be deployed on both clusters for the interim period.

Acceptance criteria

• Payload Tracker is deployed on the HCC cluster with successful connectivity to the existing shared cloud resources
• Consumer and vacuum components only run on HCC cluster (are scaled down on CRC cluster)
• SOPs are created/updated to ensure this migration process is repeatable and can be done again solely by following the SOPs
• 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
• Grafana dashboards and alerts are adjusted to include data from the new cluster
• The original deployment will continue to operate as it does today