Linkerd as lightweight alternative in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to install Linkerd CLI using curl.

Kubernetes

curl -sL https://run.linkerd.io/install | [1]

Drag options to blanks, or click blank then click option'

Abash

Bsh

Cpython

Dzsh

Attempts:

3 left

💡 Hint

Common Mistakes

Using python or zsh instead of sh causes errors.

The Linkerd CLI installation script is run using sh after downloading with curl.

2fill in blank

medium

Complete the command to check if your Kubernetes cluster is ready for Linkerd installation.

Kubernetes

linkerd [1]

Drag options to blanks, or click blank then click option'

Ainstall

Bversion

Ccheck

Ddashboard

Attempts:

3 left

💡 Hint

Common Mistakes

Using install runs installation, not a readiness check.

The linkerd check command verifies if the cluster meets requirements for Linkerd.

3fill in blank

hard

Fix the error in the command to install Linkerd control plane in Kubernetes.

Kubernetes

linkerd install | kubectl [1] -f -

Drag options to blanks, or click blank then click option'

Aget

Bcreate

Cdelete

Dapply

Attempts:

3 left

💡 Hint

Common Mistakes

Using create fails if resources exist.

Using delete removes resources.

The correct command to apply the Linkerd control plane manifest is kubectl apply -f -.

4fill in blank

hard

Fill both blanks to inject Linkerd proxy into a deployment manifest.

Kubernetes

kubectl [1] deploy -n my-namespace -o yaml | linkerd [2] - | kubectl apply -f -

Drag options to blanks, or click blank then click option'

Aget

Binject

Cdelete

Ddescribe

Attempts:

3 left

💡 Hint

Common Mistakes

Using apply instead of get to fetch manifest.

Using delete or describe incorrectly.

First, get the deployment manifest, then inject Linkerd proxy using linkerd inject.

5fill in blank

hard

Fill all three blanks to check the status of Linkerd pods in the control plane namespace.

Kubernetes

kubectl -n [1] get pods -l [2]=linkerd -o [3]

Drag options to blanks, or click blank then click option'

Alinkerd

Bapp

Cwide

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using default namespace instead of linkerd.

Using wrong label key or output format.

The Linkerd control plane runs in the linkerd namespace. Pods are labeled with app=linkerd. The -o wide option shows detailed pod info.