Service Mesh

Linkerd with viz

First, you will install the service mesh, Linkerd onto your local machine. Using the CLI, you’ll then install the control plane onto your Kubernetes cluster. Now that we have our cluster, we’ll install the Linkerd CLI and use it validate that your cluster is capable of hosting the Linkerd control plane.

(Note: if you’re using a GKE “private cluster”, there are some extra steps required before you can proceed to the next step.)

If this is your first time running Linkerd, you will need to download the linkerd command-line interface (CLI) onto your local machine. The CLI will allow you to interact with your Linkerd deployment.

To install the CLI manually, run:

curl -sL | sh

Add it to your path, like

export PATH=$PATH:/Users/<user>/.linkerd2/bin

Alternatively, if you use Homebrew, you can install the CLI with

brew install linkerd

You can also download the CLI directly via the Linkerd releases page.

Once installed, verify the CLI is running correctly with:

linkerd version

You should see the CLI version, and also Server version: unavailable. This is because you haven’t installed the control plane on your cluster. Don’t worry—we’ll fix that soon enough.

Install Linkerd the Promethues (metric store) (part of Linkerd Viz):

linkerd install | kubectl apply -f -
linkerd viz install | kubectl apply -f -

Create a test namespace or choose an existing namespace and enable Linkerd proxy injection:

kubectl create ns test
kubectl annotate namespace test

After annotating kill the existing pods to re-create pods with new annotations.

Flagger or other operators in next step requires a Kubernetes cluster v1.16 or newer and Linkerd 2.10 or newer.

Next step is to have a progressive delivery Kubernetes operator.

ISTIO, Consul

Istio, Consul support Coming Soon...

results matching ""

    No results matching ""