HYPERFLEET-655: fix RabbitMQ deployment bugs and cleanup

README.md

@@ -359,18 +359,6 @@ If pods fail with "Permission denied" or "Unable to generate access token":
 3. Ensure the K8s service account name in Helm values matches what terraform expects
 4. Verify the pod is running in the correct namespace (must match terraform's `kubernetes_namespace`)
 
-## Migration from Legacy Chart
-
-The root-level Chart.yaml is deprecated. Migrate to cloud-specific overlays:
-
-```bash
-# Old (deprecated)
-helm install hyperfleet . -f values.yaml
-
-# New (recommended)
-helm install hyperfleet charts/hyperfleet-gcp -f examples/gcp-pubsub/values.yaml
-```
-
 ## Future Cloud Support
 
 Additional cloud overlays can be added following the same pattern:

charts/hyperfleet-base/values.yaml

@@ -59,6 +59,9 @@ hyperfleet-api:
     registry: quay.io/openshift-hyperfleet
     repository: hyperfleet-api
     tag: ""  # Required: Set to specific version (e.g., "v1.0.0" or "dev-abc1234")
+  adapters:
+    cluster: []
+    nodepool: []
   database:
     # Built-in PostgreSQL for development
     postgresql:

charts/hyperfleet-gcp/values-rabbitmq.yaml

@@ -20,6 +20,7 @@ base:
 
   sentinel:
     broker:
+      type: rabbitmq
       topic: "hyperfleet-clusters"
       rabbitmq:
         url: "amqp://hyperfleet:hyperfleet-dev-password@hyperfleet-rabbitmq:5672/"