by Buoyant

Version 2.7.1



Linkerd is an ultralight service mesh for Kubernetes. It makes running services easier and safer by giving you runtime debugging, observability, metrics, reliability, and security without requiring any code changes. And now, the Buoyant Linkerd 1-Click App configures and performs a recommended deployment of Linkerd2 onto a DigitalOcean Kubernetes cluster, in the linkerd namespace. It's all done for you, in mere minutes.

The Linkerd2 CLI is recommended to interact with Linkerd2 and instructions are provided to add your specific service. As a part of a recommended deployment this 1-click contains Grafana and Prometheus included in the linkerd namespace.

This stack source is open source and community supported, and can be found at Contributions on bug fixes and features will be kindly reviewed. If you have large production needs and would like a trusted services and support partner by your side Buoyant - makers of Linkerd - have the Buoyant Enterprise Support subscription just for you.

Note: This stack requires a minimum configuration of 2 Nodes at the $10/month plan (2GB memory / 1 vCPU).

If you're interested in more controls for your whole team, check out Dive, our new SaaS "team control plane" for teams operating Kubernetes, now in private Beta.

Software Included

Getting started after deploying Linkerd

Confirm Linkerd is running:

After you have downloaded your kube config file, and are able to successfully connect to your DigitalOcean Kubernetes cluster (see if you haven’t connected to your cluster) you’ll be able to see Linkerd running in the linkerd namespace by issuing:

kubectl get deployment -n linkerd

Confirm all linkerd deployments are in a “ready” state:

NAME                     READY   UP-TO-DATE   AVAILABLE   AGE
linkerd-controller       1/1     1            1           43m
linkerd-destination      1/1     1            1           43m
linkerd-grafana          1/1     1            1           43m
linkerd-identity         1/1     1            1           43m
linkerd-prometheus       1/1     1            1           43m
linkerd-proxy-injector   1/1     1            1           43m
linkerd-sp-validator     1/1     1            1           43m
linkerd-tap              1/1     1            1           43m
linkerd-web              1/1     1            1           43m

You can get started with Linkerd in just 3 simple steps.

1.) Install the CLI (Documentation)

If this is your first time running Linkerd, you’ll need to download the command line interface (CLI) onto your local machine. You’ll use this CLI to interact with Linkerd.

Instructions here are for MacOS and Linux. For instructions on other Operating Systems see the release page.

Download and install the Linkerd client binary:

curl -sL | sh

Next, add Linkerd to your path:

export PATH=$PATH:$HOME/.linkerd2/bin

Verify that the CLI is installed by running:

linkerd version

2.) Explore Linkerd (Documentation)

With the control plane installed and running, you can now view the Linkerd dashboard by running:

linkerd dashboard

This will open your default browser and load your Linkerd dashboard.

  • Linkerd also includes Grafana to visualize all the great metrics collected by Prometheus and ships with some extremely valuable dashboards.
  • You can get to these by clicking the Grafana icon in the overview page.

3.) Adding Your Service (Documentation)

In order for your service to take advantage of Linkerd, it needs to have the proxy sidecar added to its resource definition. This is done by using the Linkerd CLI to update the definition and output YAML that can be passed to kubectl. By using Kubernetes’ rolling updates, the availability of your application will not be affected.

To add Linkerd to your service, run:

linkerd inject deployment.yml | kubectl apply -f -

API Creation

In addition to creating Linkerd via the control panel, you can also use the DigitalOcean API.

As an example, to create a 3 node DigitalOcean Kubernetes cluster made up of Basic Droplets in the SFO2 region, you can use the following curl command. You’ll need to either save your API access token to an environment variable or substitute it into the command below.

  curl -X POST -H "Content-Type: application/json" \
      -H "Authorization: Bearer '$TOKEN'" -d \
      '{"name": "choose-a-name","region": "sfo2","version": "1.17.5-do.0","node_pools": [{"size": "s-1vcpu-2gb","count": 3,"name": "choose-a-name"}]}' \

Support Details

Supported By:BuoyantBuoyant
Support URL: