[SaveAndRestore] CAO tool unable to save data topology of Service Broker deployed CB instance.

Steps to reproduce:

1. Create a 3-node Couchbase Instance running 7.0.3 with default bucket using Service Broker. Status of pods: 

   Prateeks-MacBook-Pro:couchbase-service-broker-kubernetes prateekkumar$ kubectl get pods

   NAME                                                  READY   STATUS    RESTARTS   AGE

   catalog-catalog-controller-manager-79c8b4c484-g7vcx   1/1     Running   0          7m7s

   catalog-catalog-webhook-b587f8677-8wjw2               1/1     Running   0          7m7s

   couchbase-instance-p8jpug1f-0000                      1/1     Running   0          3m6s

   couchbase-instance-p8jpug1f-0001                      1/1     Running   0          2m10s

   couchbase-instance-p8jpug1f-0002                      1/1     Running   0          73s

   couchbase-operator-654cf4c5c8-f8w6s                   1/1     Running   0          3m34s

   couchbase-operator-admission-84bbbcc844-bvh9l         1/1     Running   0          6m3s

   couchbase-service-broker-7c7459c5fc-x5xhl             1/1     Running   0          4m54s

1. Edit the Couchbase Cluster setting buckets.managed to false.
2. Delete the default Couchbase bucket through kubectl. 
3. Delete the default bucket from CB UI as well followed by loading travel-sample on the cluster.
4. Add a couple of collections to two scopes of the travel-sample bucket on the UI.
5. Run the CAO tool to save the modified topology, the command used: 

   Prateeks-MacBook-Pro:bin prateekkumar$ ./cao save --cluster couchbase-instance-p8jpug1f --path /bucket --filename save.yaml

   where couchbase-instance-p8jpug1f is the cluster name.

Error: 

Get "http://localhost:58170/pools": EOF 

Operator Logs attached along with Service Broker logs(SB logs truncated since it kept running for 10 minutes).

I'm not sure if these logs would help, so let me know if there's a way to collect logs to investigate the cao tool itself.