Not able to access External DNS enabled k8s deployment via nodejs sdk

Couchbase Server Kubernetes
1

https://couchbasecluster-0000.wayship.io:18091/ui/index.html
Administrator/password

As per this doc https://docs.couchbase.com/operator/2.0/howto-client-sdks.html#dns-based-addressing-with-external-dns the connection string should be https://console.wayship.io:18091

The nodejs sdk is throwing

/xxxxx/node_modules/couchbase/lib/bucket.js:206
  this._cb = new CBpp(bucketDsn, bucketUser, bucketPass);
             ^
Waiting for the debugger to disconnect...
CouchbaseError

The nodejs sdk code

var couchbase = require('couchbase');
var cluster = new couchbase.Cluster('https://console.wayship.io:18091', {
	// expiry: 30000,
});
// For Couchbase > 4.5 with RBAC Auth
cluster.authenticate('wayship', 'wayship');
var bucket = cluster.openBucket('wayshipdev');

let n1ql = couchbase.N1qlQuery;

// let req = bucket.query(n1ql.fromString(`INSERT INTO wayship (KEY, VALUE) VALUES ($1, $2)`, ['test', 'asdfa']));
// req.on('data', function() {
// 	debugger;
// })

// req.on('error', function() {
// 	debugger;
// })
// bucket.insert('shd', 'asdf', function(err, data) {
// 	console.log(data);
// })
bucket.upsert('testdoc', {name:'Frank'}, function(err, result) {
  if (err) throw err;

  bucket.get('testdoc', function(err, result) {
    if (err) throw err;

    console.log(result.value);
    // {name: Frank}
  });
});
2

Check your DDNS is working:

$ dig +short couchbasecluster-0000.wayship.io
13.127.66.138
$ dig +short couchbasecluster-0001.wayship.io
52.66.10.185
$ dig +short couchbasecluster-0002.wayship.io
52.66.5.35
$ dig +short console.wayship.io
$

The DNS A record is missing which appears to be the problem.

3

For context, when you expose the admin console (spec.networking.exposeAdminConsole, with spec.networking.adminConsoleType: LoadBalancer) the Operator should annotate the service couchbasecluster-ui in the deployment namespace with a DNS name label. Ensure the service is up, has an IP address allocated and that whatever you are using to push that address into DDNS is picking it up.

4

Yes I observe, Route53 is not pushing console.wayship.io to DDNS.
Neither the couchbasecluster-ui is assigned public ip.
Not Sure where i’m doing wrong.
This is how my cluster yaml looks like

apiVersion: couchbase.com/v2
kind: CouchbaseCluster
metadata:
  name: couchbasecluster
spec:
  image: couchbase/server:6.5.0
  security:
    adminSecret: cbsecret
  buckets:
    managed: true
  servers:
  - size: 3
    name: all_services
    services:
    - data
    - index
    - query
    - search
    - eventing
    - analytics
  networking:
    exposeAdminConsole: true
    adminConsoleServices:
    - data
    adminConsoleServiceType: LoadBalancer
    exposedFeatures:
    - xdcr
    - client
    - admin
    exposedFeatureServiceType: LoadBalancer
    exposedFeatureTrafficPolicy: Local
    tls:
      static:
        serverSecret: couchbase-server-tls
        operatorSecret: couchbase-operator-tls
    dns:
      domain: wayship.io
    serviceAnnotations:
      my-annotation: my-value
  logging:
    logRetentionTime: 604800s
    logRetentionCount: 20

Suggest if i missed anything

couchbasecluster-srv           ClusterIP      None            <none>                                                                     11210/TCP,11207/TCP     
couchbasecluster-ui            LoadBalancer   10.100.25.86     <pending>                                                                 18091:32125/TCP
5

Appreciate any help on this.

6

i have a similar issue, did this ever get resolved?
I have adminConsoleServiceTemplate exposed with LoadBalancer, and dns defined, and exposedFeatures set to client, I get the service/-ui service created with external ip address defined (metallb on-prem), but only the 18091 port expose…

7

Please start a new thread with the details from your environment.

8

have one here, thanks: Operator admin console exposed with LoadBalancer