> For the complete documentation index, see [llms.txt](https://doczhcn.gitbook.io/linkerd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doczhcn.gitbook.io/linkerd/index-1.md).

# 官方博客

在 buoyant (linkerd的开发者) 的官方网站上,发表有很多和likerd相关的博客文章:

<https://buoyant.io/blog/>

这里是对官方博客内容的中文翻译版本.

> 译者注: 这些博客文章对了解 linkerd 非常有帮助,而且从官方文档的写作风格上看,所有涉及到有深度或者需要谈论细节的时候,基本都是给出一个链接指到博客上的某个文章.因此,考虑将官方博客的文章逐一翻译过来.

## 内容

当前已经翻译完成的内容:

* [超越轮循:为了延迟的负载均衡](/linkerd/index-1/beyond-round-robin-load-balancing-for-latency.md)
* [LINKERD：用于微服务的TWITTER风格可操作性](/linkerd/index-1/linkerd-twitter-style-operability-for-microservices.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doczhcn.gitbook.io/linkerd/index-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.