Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-2418

Hashicorp Consul service mesh support

    XMLWordPrintable

Details

    • 1

    Description

      Request for supporting Hashicorp Consul service mesh from Kore Wireless.

      From customer:

      I was originally working with you over the couchbase forums (https://forums.couchbase.com/t/couchbase-helm-chart-and-hashicorp-consul-service-mesh/31682/5) . I have been working on implementing service mesh at my company for some time now and I am working on enabling and documenting use for currently deployed systems. If any testing or anything is needed I can definitely make time available.

      Just wanted to say thank you for taking time to look into this and forward my company information. https://www.korewireless.com/

      The annotations can be added via the CRD and Helm. Need to confirm this is all that is required.

      For Helm:

      cluster:
        servers:
          default:
            pod:
              metadata:
                annotations:
                  consul.hashicorp.com/connect-inject: "true"   
                  consul.hashicorp.com/connect-service: couchbase-test
      

      For the standard CRD, this just gets nested into the appropriate bit of the server section.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          khells Brandon Tate added a comment -

          Transparent proxy was just released with the most recent version of consul. So for any versions under 1.10.0 deployed through helm then this would not be an issue

          khells Brandon Tate added a comment - Transparent proxy was just released with the most recent version of consul. So for any versions under 1.10.0 deployed through helm then this would not be an issue

          The user reported some issues with readiness probes failing until:

          After some more testing it looks like I had to disable the transparent-proxy with this annotation

          consul.hashicorp.com/transparent-proxy: "false"
          

          The proxy redirects all traffic through the sidecar which was what was causing the issues but disabling it was enough to get it running without errors. For future use I will most likely be able to exclude redirection of traffic using some other annotations here https://www.consul.io/docs/connect/transparent-proxy . I also will be doing some testing on enabling service mesh on the operator and routing all of my traffic through the sidecars.

          patrick.stephens Patrick Stephens (Inactive) added a comment - - edited The user reported some issues with readiness probes failing until: After some more testing it looks like I had to disable the transparent-proxy with this annotation consul.hashicorp.com/transparent-proxy: "false" The proxy redirects all traffic through the sidecar which was what was causing the issues but disabling it was enough to get it running without errors. For future use I will most likely be able to exclude redirection of traffic using some other annotations here https://www.consul.io/docs/connect/transparent-proxy . I also will be doing some testing on enabling service mesh on the operator and routing all of my traffic through the sidecars.

          People

            anil Anil Kumar (Inactive)
            patrick.stephens Patrick Stephens (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty