Skip to content

Latest commit

 

History

History
312 lines (264 loc) · 8.36 KB

README.md

File metadata and controls

312 lines (264 loc) · 8.36 KB

Traffic routing on K8s with Consul Connect

This example shows how to using HTTP paths to route traffic between two versions of a service in Kubernetes

If you do not have access to a Kubernetes cluster, the script in ../consul_k8s allows you to create a Kubernetes cluster with Consul installed using Docker on your local machine.

Configuring Helm

To enable Consul Service Mesh the following values must be configured in the official helm chart:

global
  image: "consul:1.6.1"
  imageK8S:  "hashicorp/consul-k8s:0.9.2"

connectInject:
  enabled: true
  imageEnvoy: "envoyproxy/envoy:v1.10.0"
  
  centralConfig:
    enabled: true

client:
  enabled: true
  grpc: true

L7 configuration

To enable traffic splitting the following configuration needs to be set:

service-defaults for web service setting HTTP protocol

kind = "service-defaults"
name = "web"
protocol = "http"

service-defaults for api service setting HTTP protocol

kind = "service-defaults"
name = "api"
protocol = "http"

service-r olverfor api service allowing subset based on service catalog metadata

kind = "service-resolver"
name = "api"

# Filtering options for subsets can be found at the following link
# https://www.consul.io/api/health.html#filtering-2

# Using a default_subset will route traffic to the subset specified in the value when no `traffic-splitter` is present. 
# Configuring the `traffic-splitter` overrides this default.
default_subset = "v1"

subsets = {
  v1 = {
    filter = "Service.Meta.version == 1"
  }
  v2 = {
    filter = "Service.Meta.version == 2"
  }
}

service-router to configure path based routing to a specific subset.

The following example routes traffic between service subsets using HTTP paths.

https://www.consul.io/docs/agent/config-entries/service-router.html

kind = "service-router",
name = "api"

routes = [
  {
    match {
      http {
        path_prefix="/v1"
      }
    }

    destination {
      service = "api"
      service_subset = "v1"
    }
  },
  {
    match {
      http {
        path_prefix="/v2"
      }
    }

    destination {
      service = "api"
      service_subset = "v2"
    }
  },
]

Loading configuration

To load the configuration into Consul it is possible to use three methods:

  • Consul CLI consul config write file.hcl, hcl or json formatted files
  • PUT request to the API (json only)
  • Using a Kubernetes job

The following example shows how it is possible to use a Kubernetes job to set multiple configuration files. There are updates to the K8s integration which will remove the need for the job and will allow a config map to be referenced by K8s annotation and automatically injected.

---
apiVersion: v1
kind: ConfigMap
metadata:
  name: central-config-routing
data:
  1_web_defaults.hcl: |
    kind = "service-defaults"
    name = "web"
    protocol = "http"
  2_api_defaults.hcl: |
    kind = "service-defaults"
    name = "api"
    protocol = "http"
  3_api_resolver.hcl: |
    kind = "service-resolver"
    name = "api"

    # https://www.consul.io/api/health.html#filtering-2
    # # Show Node.Meta demonstration showing performance testing a new instance type
    default_subset = "v1"

    subsets = {
      v1 = {
        filter = "Service.Meta.version == 1"
      }
      v2 = {
        filter = "Service.Meta.version == 2"
      }
    }

---
apiVersion: batch/v1
kind: Job
metadata:
  name: central-config-routing
  labels:
    app: central-config-routing
spec:
  template:
    spec:
      restartPolicy: Never
      volumes:
      - name: central-config
        configMap:
          name: central-config-routing
      containers:
      - name: central-config-split
        image: "nicholasjackson/consul-envoy:v1.6.1-v0.10.0"
        imagePullPolicy: Always
        env:
        - name: "CONSUL_HTTP_ADDR"
          value: "consul-consul-server:8500"
        - name: "CONSUL_GRPC_ADDR"
          value: "consul-consul-server:8502"
        - name: "CENTRAL_CONFIG_DIR"
          value: "/config"
        volumeMounts:
        - name: "central-config"
          readOnly: true
          mountPath: "/config"

Configuring metadata

For the service-resolver to include a service in a particular subset, Consul metadata is used. Configuring the metadata for the service in Consul's service catalog is done by using the K8s annotations, e.g.

  template:
    metadata:
      labels:
        app: api-v1
      annotations:
        "consul.hashicorp.com/connect-inject": "true"
        "consul.hashicorp.com/service-meta-version": "1"
        "consul.hashicorp.com/service-tags": "v1"

Running the example

With a running Kubernetes cluster and the Consul Helm chart installed a simple 2 tier application can be run using the following command:

➜ kubectl apply -f traffic_routing.yml
configmap/central-config-routing created
job.batch/central-config-routing created
service/web-service created
deployment.apps/web-deployment created
deployment.apps/api-deployment-v1 created
deployment.apps/api-deployment-v2 created

This config contains the following elements

  • Web application - entry point
  • API version 1 - upstream service
  • API version 2 - upstream service
  • K8s Service pointed at Web application
  • Config map containing L7 config
  • Job to load L7 config

It should take a couple of seconds for the application to get up and running:

➜ kubectl get pods
NAME                                                              READY   STATUS      RESTARTS   AGE
api-deployment-v1-5bd59988f8-h82pm                                2/2     Running     0          28s
api-deployment-v2-6dd66bdb6f-864kk                                2/2     Running     0          28s
central-config-routing-5nmk2                                      0/1     Completed   0          28s
consul-consul-connect-injector-webhook-deployment-c46d9888rq7x6   1/1     Running     0          16m
consul-consul-nb68d                                               1/1     Running     0          16m
consul-consul-server-0                                            1/1     Running     0          16m
web-deployment-66488ddb9-z2x92                                    2/2     Running     0          28s

You can access the Kubernetes service by using the command kubectl port-forward to forward a port from your local machine to the service for the web application in your Kubernetes cluster.

kubectl port-forward svc/web-service 9090
Forwarding from 127.0.0.1:9090 -> 9090
Forwarding from [::1]:9090 -> 9090

The web service can then be accessed at http://localhost:9090. When the web service is called it will make an upstream call to the API service. You should see the following output in your terminal.

➜ curl localhost:9090
{
  "name": "web",
  "type": "HTTP",
  "duration": "6.137322ms",
  "body": "Hello World",
  "upstream_calls": [
    {
      "name": "api-v1",
      "uri": "http://localhost:9091",
      "type": "HTTP",
      "duration": "10.9µs",
      "body": "Response from API v1"
    }
  ]
}

Alternately you can view the UI in your browser at http://localhost:9090.

Initially there is no traffic-router configured the service will always resolve to the default subset which is the v1 api.

To enable traffic routing apply the central config to consul using the CLI

➜ consul config write 1_api-router.hcl

Now when the web endpoint is curled traffic will be split between v1 and v2 depending on the path used.

➜ curl  localhost:9090/v1
{
  "name": "web",
  "type": "HTTP",
  "duration": "10.967173ms",
  "body": "Hello World",
  "upstream_calls": [
    {
      "name": "api-v1",
      "uri": "http://localhost:9091",
      "type": "HTTP",
      "duration": "10.3µs",
      "body": "Response from API v1"
    }
  ]
}

➜ curl localhost:9090/v2
{
  "name": "web",
  "type": "HTTP",
  "duration": "10.151383ms",
  "body": "Hello World",
  "upstream_calls": [
    {
      "name": "api-v2",
      "uri": "http://localhost:9091",
      "type": "HTTP",
      "duration": "143.298µs",
      "body": "Response from API v2"
    }
  ]
}

Many more features can be used for route configuration, all of the options can be found in the documentation at: https://www.consul.io/docs/agent/config-entries/service-router.html