Agent attempts to fallback to http polling when no http addresses exist

On a CAO cluster with 1 node, using server 7.1, we're failing to connect to the bucket when adding documents. We receive this error from bucket.WaitUntilReady:

unambiguous timeout | {"InnerError":{"InnerError":{"InnerError":{},"Message":"unambiguous timeout"}},"OperationID":"WaitUntilReady","Opaque":"","TimeObserved":60001318307,"RetryReasons":["NOT_READY","BUCKET_NOT_FOUND"],"RetryAttempts":128,"LastDispatchedTo":"","LastDispatchedFrom":"","LastConnectionID":""} 

This only happens with 1 node (if we change to 3 nodes, the test passes fine), and also only happens on 7.1 (on 7.0.3, the test passes fine.). The bucket is responding to API calls from the operator via /pools/default/buckets... and also appears on the server UI.

I've attached cbopinfo, cbinfo, the operator logs, and the SDK logs from gocb.SetLogger(gocb.VerboseStdioLogger())