Kubernetes Documentation

[tulioric]

What happened?

The search experience on kubernetes.io has become extremely frustrating.

When searching for technical terms, the results frequently prioritize "Discuss" pages or community content instead of the official documentation under /docs/.

This creates confusion and significantly slows down workflows for users who are trying to find authoritative documentation.

What did you expect to happen?

When searching on kubernetes.io, I expect:

• Official documentation pages (/docs/) to be prioritized.
• API reference, Concepts, Tasks, and Tutorials to appear before community discussions.
• A reliable search experience comparable to using site:kubernetes.io/docs on Google.

Why this is a problem

Kubernetes is a production-critical platform. Many engineers rely on fast access to accurate documentation.

Currently:

• Search results often surface Discuss pages first.
• The official documentation is harder to find.
• The experience feels inconsistent and unreliable.

This generates unnecessary friction and frustration for users who depend on the documentation daily.

Steps to reproduce

1. Go to https://kubernetes.io
2. Use the search bar
3. Search for common technical terms (e.g., "initContainer", "RBAC", "CNI", "CRD")
4. Observe that community/Discuss results are often prioritized over official docs

Suggested improvements

• Prioritize /docs/ content in search ranking.
• Option to filter results by "Documentation only".
• Clear separation between community content and official documentation.
• Improve indexing relevance for technical terms.

Additional context

Currently, using Google with:

site:kubernetes.io/docs <term>

provides significantly better results than the official search.

That indicates a discoverability problem within the site itself.

---

Thank you for maintaining Kubernetes documentation — improving search relevance would dramatically improve the developer experience.

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.