Create chrome-service-stage namespace on hccs01ue1 cluster for multicluster migration.

Tasks

• Create namespace file: data/services/insights/chrome-service/namespaces/hccs01ue1-chrome-service-stage.yml
• Use same namespace name: chrome-service-stage (must match crcs02ue1)
• Reference HCC stage environment: /products/hcc/environments/stage.yml
• Share existing RDS database from crcs02ue1 via vault-secret mounting
• Share existing CloudWatch from crcs02ue1 via vault-secret
• Remove networkPoliciesAllow references to 3scale (HCC uses Gateway API)
• Add networkPoliciesAllow for openshift-customer-monitoring.hccs01ue1.yml
• Copy managedResourceTypes from source namespace

Acceptance Criteria

• Namespace file created with correct cluster and environment references
• RDS credentials mounted via vault-secret with qontract.ignore_reconcile_time annotation
• Network policies reference only hccs01ue1 namespaces
• No duplicate AWS resources (only vault-secret mounts)

Related Documentation

• docs/tenant-services/console.redhat.com/app-sops/frontend-operator/frontend-multicluster.md
• .claude/skills/hcc-multicluster-dual-deployment/SKILL.md