Go SDK Doc Upserts fail on 7.1 with 1 CB node

Strange issue; some of our tests only really need 1 server pod, instead of the usual 3. Also, some of our tests use the Go SDK (2.3.0) to upsert docs; the only time both of these happen seems to be TestGSIWithCollections. This test is fine on 7.0, but with 7.1 (build 1914) the doc upserts fail; increasing the cluster size (to anything >1) has the upserts work fine and the test pass. Changing other doc insert tests to use only 1 server pod (for example, TestAnalyticsCreateDataSet) causes the same error:

util.go:1255: ambiguous timeout | {"InnerError":{"InnerError":{"InnerError":{},"Message":"ambiguous timeout"}},"OperationID":"Set","Opaque":"0x0","TimeObserved":30000401291,"RetryReasons":null,"RetryAttempts":0,"LastDispatchedTo":"","LastDispatchedFrom":"","LastConnectionID":""} 

To clarify; upserts into a 1-node Couchbase cluster seem to no longer work with 7.1. While I'm not sure how much of a concern this is (do we support 1 node clusters?) it may be indicative of a deeper problem. I'm also not sure of the expected compatibility for the SDKs with Server 7.1.

Attached logs (including gocb verbose logs from the test). Looks suspect:

GOCB 17:38:43.493332 memdclient.go:775: Memdclient `test-couchbase-rvghm-0000.test-couchbase-rvghm.test-gnrp5.svc.cluster.local:11210/0xc000476a90` Failed to perform select bucket against server (bucket not found)GOCB 17:38:43.493609 memdpipelineclient.go:233: Pipeline Client 0xc000533200 failed to bootstrap: bucket not found