Skip to content
Gauge

ax-check.com

by Gauge

Linkerd

linkerd.io

ax-check.com

Checked 28 October 2026

C

55/100

Agents haven’t verified setup

Linkerd's quickstart works, but no AI-ready docs index exists

Getting Started gives copyable install commands and a working demo walkthrough. But there's no llms.txt or Markdown version of the homepage, so agents must parse HTML.

4 fixes to start with

Concrete changes, backed by what we found.

Onboarding

Resolve the blocker that stopped agent setup.

Agents cannot progress through onboarding without human help. Provide an agent-accessible path through authentication and setup.

Docs

Return Markdown when clients request text/markdown.

Homepage returned text/html even when text/markdown was requested; no Markdown representation offered.

Docs

Add links to your product documentation and quickstart in /llms.txt.

https://linkerd.io/llms.txt returns HTTP 404, so no documentation index exists.

Docs

Publish a text or Markdown version of the quickstart.

No site-published Markdown guide; /llms.txt returns 404 and homepage Markdown negotiation yields HTML.

Recorded coding sessions

Same task, 3 models, no linkerd.io account. Recorded 28 October 2026 on Pi.

3 recorded · 21s

21s · recorded

Session findings

Select a finding to see it in context.

piv0.84.2
modelQwen 3.8 Maxcwd/sandbox/repo
Help me build a simple example using Linkerd. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.
Thinking…

The user is asking about Linkerd. Linkerd is an open-source service mesh, and it's not a hosted product with an SDK/API that can be used without a cluster. Let me check the repository context.

The instructions state: "If this product doesn't have an actionable developer workflow, state that clearly and stop." Linkerd requires a Kubernetes cluster — this falls under a local service stack / long-running commands. Therefore, following the instructions, I should state that clearly and stop.

Also regarding "how the pricing works" — Linkerd's open source is free (Apache 2.0), and enterprise pricing is quote-based via Buoyant. I can mention this briefly.

Let me quickly check the repository to see whether there's any Linkerd-related content.

ls /sandbox/repo && rg -il linkerd /sandbox/repo | head
/bin/bash: line 1: rg: command not found
/bin/bash: line 1: rg: command not found
Thinking…

Empty repository (ls shows nothing). grep unavailable. Nothing related to Linkerd. Per the constraints, stopping.

The repo is empty and there's nothing Linkerd-related to build on here. Per your constraints, I'm stopping rather than proceeding.

Why I'm blocked:

  • Linkerd is a service mesh that runs inside a Kubernetes cluster. There is no hosted Linkerd product with an SDK/API I can call directly — every "quickstart" path (linkerd install | kubectl apply -f -, deploying demo apps, linkerd check) requires a running cluster, which means starting a local service stack (kind/minikube/k3d) and waiting on long-running commands. That's exactly what you told me not to do, so I'm saying so plainly and stopping.

Pricing (brief):

  • Linkerd Open Source (Stable) — free, Apache 2.0 license. Includes the data plane, mTLS, retries, traffic splits, etc.
  • Linkerd Enterprise (sold via Buoyant) — quote-based/annual subscription, no public pricing. Adds multi-cluster failover, CNI/audit log integrations, priority support, and extension access. You have to contact Buoyant sales for a number.
  • No usage-based/metered billing — pricing is per-cluster/subscription, not per-request.

Will it be easy for me to manage? Honestly: not in this environment. I can help you write manifests, Helm values, ServiceProfiles, traffic-split configs, and CI scripts — that's file-based work I'm good at. But I can't operate it here because everything operational (installing, verifying, observing traffic) requires a live Kubernetes cluster, which is out of scope under your "no local stacks, no long-running commands" rule. In an environment where a cluster already exists and linkerd/kubectl are pre-configured, management would be reasonably easy — Linkerd's CLI is simple and its config is declarative.

If you want to proceed later, options that would fit your constraints:

  1. Point me at an existing cluster (kubeconfig already working) and I'll only run quick, non-blocking commands.
  2. Or I can produce a complete example as files only (namespace, deployment, ServiceProfile, TrafficSplit, mTLS annotations) for you to apply yourself — no cluster needed on my end. Just say the word.

AX Fundamentals

23 checks. Open an area for details.

This check is a quick preview. Test more tasks and models with Gauge Agents.

Test your product with Gauge Agents

AX Check by Gauge