feat: add auto-generated llms.txt file for all localizations

[xirehat]

add auto-generated llms.txt file for all localizations.

Closes: #51544

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign nate-double-u for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	b6d2a49
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/6884f3a1dfa70e00082e931b
😎 Deploy Preview	https://deploy-preview-51707--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[seokho-son]

Hi @xirehat,

I've just read issue #51544.
Although it doesn't yet have the triage/accepted label, it seems to have received positive feedback in the comments.

That said, I believe @shurup, the original proposer, may have been waiting for the triage/accepted label and might already have a plan in mind for contributing further to implement the suggestion.

Ideally, we would move forward with a PR after the issue has been officially accepted. (and assignment a contributor who is going to work with) However, since already an open PR, why not use it as a basis for further discussion and refinement?

While I'm not an official reviewer for this topic, I'd like to suggest that @xirehat coordinate with @shurup to discuss how best to integrate the ideas—possibly including the content in LLM.txt.

@shurup, what do you think?

[shurup]

I believe @shurup, the original proposer, may have been waiting for the triage/accepted label and might already have a plan in mind for contributing further to implement the suggestion.

Thanks, Seokho! Actually, I don't have the capacity to commit to implementing it soon, so I'm happy to see anyone in the community handling this issue (as soon as it's accepted) 🙏

However, in my understanding, it's better not to create a fully auto-generated llms.txt, since we can get more value from this file if we provide a better context and structure (rather than merely listing all content available via a regular web browser). E.g.:

• We can provide not only links, but also give a brief description of Kubernetes as a technology (with basic concepts and all docs-related links) and as a project (with a governance model, community-related links, perhaps even including third-party links to the related ecosystem, such as Kubernetes SIGs, certifications, playgrounds, etc.).
• For all blog articles, we can specify that the latest published information should prevail.

At the same time, while contemplating that, I guess making a perfect llms.txt is a huge effort. And probably we'd better start with something small 😅