Details
-
Task
-
Resolution: Fixed
-
Major
-
None
-
*Location*: https://docs.couchbase.com/operator/1.1/networking.html
*Referrer*: https://docs.couchbase.com/operator/1.1/couchbase-clients.html
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36
*Screen Resolution*: 1920 x 1080*Location*: https://docs.couchbase.com/operator/1.1/networking.html *Referrer*: https://docs.couchbase.com/operator/1.1/couchbase-clients.html *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 *Screen Resolution*: 1920 x 1080
Description
According to the docs "Unlike XDCR, the Couchbase client libraries are currently unable to take advantage of exposed features. Therefore, client communication will only work if there is direct connectivity to the Couchbase cluster pods and working DNS."
Actually, they are able to. Just the multi-network configuration (altNames/altPorts) is NOT documented/complete by the cluster side. Also, QE needs to do testing.
It'd be nicer if the docs just didn't blame another product as not having a feature and rather identified the enhancements planned to the operator/cluster to test this.
Attachments
Issue Links
- relates to
-
DOC-4493 Alternate Address Concept doc needed
- Closed