Deploy Single Consul Datacenter Across Multiple Kubernetes Clusters

This page describes deploying a single Consul datacenter in multiple Kubernetes clusters, with servers running in one cluster and only Consul on Kubernetes components in the rest of the clusters. This example uses two Kubernetes clusters, but this approach could be extended to using more than two.

Requirements

• consul-k8s v1.0.x or higher, and Consul 1.14.x or higher
• Kubernetes clusters must be able to communicate over LAN on a flat network.
• Either the Helm release name for each Kubernetes cluster must be unique, or global.name for each Kubernetes cluster must be unique to prevent collisions of ACL resources with the same prefix.

Prepare Helm release name ahead of installs

The Helm release name must be unique for each Kubernetes cluster. The Helm chart uses the Helm release name as a prefix for the ACL resources that it creates, such as tokens and auth methods. If the names of the Helm releases are identical, or if global.name for each cluster is identical, subsequent Consul on Kubernetes clusters will overwrite existing ACL resources and cause the clusters to fail.

Before proceeding with installation, prepare the Helm release names as environment variables for both the server and client install.

  $ export HELM_RELEASE_SERVER=server  $ export HELM_RELEASE_CONSUL=consul  ...  $ export HELM_RELEASE_CONSUL2=consul2

Deploying Consul servers in the first cluster

First, deploy the first cluster with Consul servers according to the following example Helm configuration.

global:  datacenter: dc1  tls:    enabled: true    enableAutoEncrypt: true  acls:    manageSystemACLs: true  gossipEncryption:    secretName: consul-gossip-encryption-key    secretKey: keyserver:  exposeService:    enabled: true    type: NodePort    nodePort:      ## all are random nodePorts and you can set your own      http: 30010      https: 30011      serf: 30012      rpc: 30013      grpc: 30014ui:  service:    type: NodePort

Note that this will deploy a secure configuration with gossip encryption, TLS for all components and ACLs. In addition, this will enable the Consul Service Mesh and the controller for CRDs that can be used later to verify the connectivity of services across clusters.

The UI's service type is set to be NodePort. This is needed to connect to servers from another cluster without using the pod IPs of the servers, which are likely going to change.

Other services are exposed as NodePort services and configured with random port numbers. In this example, the grpc port is set to 30014, which enables services to discover Consul servers using gRPC when connecting from another cluster.

To deploy, first generate the Gossip encryption key and save it as a Kubernetes secret.

$ kubectl create secret generic consul-gossip-encryption-key --from-literal=key=$(consul keygen)

Now install Consul cluster with Helm:

$ helm install ${HELM_RELEASE_SERVER} --values cluster1-values.yaml hashicorp/consul

Once the installation finishes and all components are running and ready, the following information needs to be extracted (using the below command) and applied to the second Kubernetes cluster.

• The CA certificate generated during installation
• The ACL bootstrap token generated during installation

$ kubectl get secret ${HELM_RELEASE_SERVER}-consul-ca-cert ${HELM_RELEASE_SERVER}-consul-bootstrap-acl-token --output yaml > cluster1-credentials.yaml

Deploying Consul Kubernetes in the second cluster

Switch to the second Kubernetes cluster where Consul clients will be deployed that will join the first Consul cluster.

$ kubectl config use-context <K8S_CONTEXT_NAME>

First, apply the credentials extracted from the first cluster to the second cluster:

$ kubectl apply --filename cluster1-credentials.yaml

To deploy in the second cluster, the following example Helm configuration will be used:

global:  enabled: false  datacenter: dc1  acls:    manageSystemACLs: true    bootstrapToken:      secretName: cluster1-consul-bootstrap-acl-token      secretKey: token  tls:    enabled: true    caCert:      secretName: cluster1-consul-ca-cert      secretKey: tls.crtexternalServers:  enabled: true  # This should be any node IP of the first k8s cluster or the load balancer IP if using LoadBalancer service type for the UI.  hosts: ["10.0.0.4"]  # The node port of the UI's NodePort service or the load balancer port.  httpsPort: 31557  # Matches the gRPC port of the Consul servers in the first cluster.  grpcPort: 30014  tlsServerName: server.dc1.consul  # The address of the kube API server of this Kubernetes cluster  k8sAuthMethodHost: https://kubernetes.example.com:443connectInject:  enabled: true

Note the references to the secrets extracted and applied from the first cluster in ACL and TLS configuration.

The externalServers.hosts and externalServers.httpsPort refer to the IP and port of the UI's NodePort service deployed in the first cluster. Set the externalServers.hosts to any Node IP of the first cluster, which can be seen by running kubectl get nodes --output wide. Set externalServers.httpsPort to the nodePort of the cluster1-consul-ui service. In our example, the port is 31557.

$ kubectl get service cluster1-consul-ui --context cluster1NAME                 TYPE       CLUSTER-IP    EXTERNAL-IP   PORT(S)         AGEcluster1-consul-ui   NodePort   10.0.240.80   <none>        443:31557/TCP   40h

The grpcPort: 30014 configuration refers to the gRPC port number specified in the NodePort configuration in the first cluster.

Set the externalServer.tlsServerName to server.dc1.consul. This the DNS SAN (Subject Alternative Name) that is present in the Consul server's certificate. This is required because the connection to the Consul servers uses the node IP, but that IP isn't present in the server's certificate. To make sure that the hostname verification succeeds during the TLS handshake, set the TLS server name to a DNS name that is present in the certificate.

Next, set externalServers.k8sAuthMethodHost to the address of the second Kubernetes API server. This should be the address that is reachable from the first cluster, so it cannot be the internal DNS available in each Kubernetes cluster. Consul needs it so that consul login with the Kubernetes auth method will work from the second cluster. More specifically, the Consul server will need to perform the verification of the Kubernetes service account whenever consul login is called, and to verify service accounts from the second cluster, it needs to reach the Kubernetes API in that cluster. The easiest way to get it is from the kubeconfig by running kubectl config view and grabbing the value of cluster.server for the second cluster.

Now, proceed with the installation of the second cluster.

$ helm install ${HELM_RELEASE_CONSUL} --values cluster2-values.yaml hashicorp/consul

Verifying the Consul Service Mesh works

Now that the Consul cluster spanning across multiple k8s clusters is up and running, deploy two services in separate k8s clusters and verify that they can connect to each other.

First, deploy static-server service in the first cluster:

---apiVersion: consul.hashicorp.com/v1alpha1kind: ServiceIntentionsmetadata:  name: static-serverspec:  destination:    name: static-server  sources:    - name: static-client      action: allow---apiVersion: v1kind: Servicemetadata:  name: static-serverspec:  type: ClusterIP  selector:    app: static-server  ports:    - protocol: TCP      port: 80      targetPort: 8080---apiVersion: v1kind: ServiceAccountmetadata:  name: static-server---apiVersion: apps/v1kind: Deploymentmetadata:  name: static-serverspec:  replicas: 1  selector:    matchLabels:      app: static-server  template:    metadata:      name: static-server      labels:        app: static-server      annotations:        "consul.hashicorp.com/connect-inject": "true"    spec:      containers:        - name: static-server          image: hashicorp/http-echo:latest          args:            - -text="hello world"            - -listen=:8080          ports:            - containerPort: 8080              name: http      serviceAccountName: static-server

Note that defining a Service intention is required so that our services are allowed to talk to each other.

Next, deploy static-client in the second cluster with the following configuration:

apiVersion: v1kind: Servicemetadata:  name: static-clientspec:  selector:    app: static-client  ports:    - port: 80---apiVersion: v1kind: ServiceAccountmetadata:  name: static-client---apiVersion: apps/v1kind: Deploymentmetadata:  name: static-clientspec:  replicas: 1  selector:    matchLabels:      app: static-client  template:    metadata:      name: static-client      labels:        app: static-client      annotations:        "consul.hashicorp.com/connect-inject": "true"        "consul.hashicorp.com/connect-service-upstreams": "static-server:1234"    spec:      containers:        - name: static-client          image: curlimages/curl:latest          command: [ "/bin/sh", "-c", "--" ]          args: [ "while true; do sleep 30; done;" ]      serviceAccountName: static-client

Once both services are up and running, try connecting to the static-server from static-client:

$ kubectl exec deploy/static-client -- curl --silent localhost:1234"hello world"

A successful installation would return hello world for the above curl command output.