Value Statement

Search supports hub cluster rename.

Definition of Done for Engineering Story Owner (Checklist)

1. Watch MCH for changes to hubClusterName and update the collector deployment.
2. Clean up database resources using the old cluster name.

Implementation Option 1

• We could query for cluster names where  data->_hubClusterResource=true
• This should only return 1 cluster.
• If we get 2 or more clusters, it means that there was a rename.
• We don’t know which one is the current name, but we can delete both and let the collector re-populate the current data.
• This would create a short period where data is missing.

Option 2

• Obtain the current hubClusterName from MCH and use in the query to validate that no other cluster has resources with data->_hubClusterResource=true

Option 3

• Watch incoming requests. If resources contain the property `_hubClusterResource`, then that's the current hub.

  Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.