Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

CoreDNS

      +
      CoreDNS is the de facto cloud-native standard, and the preferred DNS provider for Couchbase deployments that are managed by the Autonomous Operator.

      Overview

      Locating services that are executing on containers on an orchestration engine like Kubernetes is, of course, fundamental. In Kubernetes, Domain Name Services (DNS) is used within the Kubernetes cluster to assign names to pods and services. CoreDNS is the recommended Kubernetes DNS provider.

      When using the Couchbase Autonomous Operator to deploy Couchbase onto a Kubernetes cluster, you will want to be aware of how Couchbase resources such as CouchbaseClusters, CouchbaseBuckets, and so on are identified by applications executing in other pods which are in turn providing other services. A Couchbase cluster in Kubernetes will by default create DNS SRV records for looking up and accessing services on a Couchbase cluster.

      coredns overview

      Get Started

      CoreDNS is the preferred and most common Kubernetes DNS provider. As such, it provides Domain Name Services (DNS) for locating pods and services that are created by the Couchbase Autonomous Operator when you create Kubernetes resources based on Couchbase Custom Resource Definitions (CRDs).

      When deploying Couchbase to your Kubernetes environment using the Couchbase Autonomous Operator, you should first consider the concepts associated with setting up Couchbase as covered on the Couchbase Networking page, then look to how you would use DNS in Public Networking or setting up DNS propagation with Inter-Kubernetes Networking. Accessing Couchbase Services is covered on the page Configure Client SDKs.