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.

A newer version of this documentation is available.

View Latest

Configure Node Port Networking

      +
      This guide shows you how to configure node port networking.

      Node port networking allows connection to a Couchbase cluster when you have access to the Kubernetes node network. It cannot be secured and has no stable client connection method. Its use is highly discouraged.

      Couchbase Cluster Configuration

      apiVersion: couchbase.com/v2
kind: CouchbaseCluster
spec:
  networking:
    exposeAdminConsole: true (1)
    adminConsoleServiceTemplate:
      spec:
        type: NodePort
    exposedFeatures: (2)
    - client
    exposedFeatureServiceTemplate:
      spec:
        type: NodePort
      1 couchbaseclusters.spec.networking.exposeAdminConsole is enabled to allow the creation of a service pointing to the Couchbase admin port. The node port can be accessed on any Kubernetes node and will provide a degree of high-availability to a client connecting to it. However as node IP addresses may vary during the life cycle of a Kubernetes cluster it is considered unstable and may cause clients to fail.
      2 couchbaseclusters.spec.networking.exposedFeatures defines the client feature set, meaning all enabled services are exposed. This also causes a per-pod service to be created allowing direct access by a client to each pod as required.