Skip to content

docs: Adding localization support for zh #853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

docs: Adding localization support for zh #853

wants to merge 8 commits into from

Conversation

hitsub2
Copy link
Contributor

@hitsub2 hitsub2 commented Jun 11, 2025

What does this PR do?

🛑 Please open an issue first to discuss any significant work and flesh out details/direction. When we triage the issues, we will add labels to the issue like "Enhancement", "Bug" which should indicate to you that this issue can be worked on and we are looking forward to your PR. We would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

add zh locale support for #634

Motivation

More

  • Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
  • Mandatory for new blueprints. Yes, I have added a example to support my blueprint PR
  • Mandatory for new blueprints. Yes, I have updated the website/docs or website/blog section for this feature
  • Yes, I ran pre-commit run -a with this PR. Link for installing pre-commit locally

For Moderators

  • E2E Test successfully complete before merge?

Additional Notes

@hitsub2 hitsub2 changed the title docs: adding localization support for zh docs: Adding localization support for zh Jun 12, 2025
@hitsub2
Copy link
Contributor Author

hitsub2 commented Jun 12, 2025

need to re-build for successfully deployment:

npm run build

@nabuskey
Copy link
Collaborator

Thanks for this! I can't read Chinese so I can't comment on the contents of the guide itself. However, for the AI contents I suggest move that to the AI on EKS repository. https://github.com/awslabs/ai-on-eks

@hitsub2
Copy link
Contributor Author

hitsub2 commented Jun 25, 2025

However, for the AI contents I suggest move that to the AI on EKS repository. https://github.com/awslabs/ai-on-eks

I think I can make another pr to ai-on-eks, but the existing data-on-eks still has AI-on-EKS section that need translation, right?

@hitsub2
Copy link
Contributor Author

hitsub2 commented Jun 25, 2025

Thanks for this! I can't read Chinese so I can't comment on the contents of the guide itself.

The translation was done by Amazon Q CLI, and then made some modifications by human review.

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Aug 3, 2025

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Aug 3, 2025
@vara-bonthu vara-bonthu removed the stale label Aug 8, 2025
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Sep 8, 2025

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Sep 8, 2025
@hitsub2
Copy link
Contributor Author

hitsub2 commented Sep 10, 2025

still in work to make sure all the content translated correctly.

@github-actions github-actions bot removed the stale label Sep 11, 2025
@hitsub2
Copy link
Contributor Author

hitsub2 commented Sep 16, 2025 •
edited
Loading

Translation is done.

some translated page example:
Homepage:

image

DataHub on EKS:
image

@hitsub2
Copy link
Contributor Author

hitsub2 commented Sep 16, 2025

When running npm run build, it reports broken anchors, it is just warning we can ignore it by configure website/docusaurus.config.js, for now I just let it report.

[WARNING] Docusaurus found broken anchors!

Please check the pages of your site in the list below, and make sure you don't reference any anchor that does not exist.
Note: it's possible to ignore broken anchors with the 'onBrokenAnchors' Docusaurus configuration, and let the build pass.

Exhaustive list of all broken anchors found:
- Broken anchor on source page path = /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices:
   -> linking to #核心架构 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%A0%B8%E5%BF%83%E6%9E%B6%E6%9E%84)
   -> linking to #关键功能 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E5%85%B3%E9%94%AE%E5%8A%9F%E8%83%BD)
   -> linking to #连接器生态系统 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E8%BF%9E%E6%8E%A5%E5%99%A8%E7%94%9F%E6%80%81%E7%B3%BB%E7%BB%9F)
   -> linking to #查询优化 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%9F%A5%E8%AF%A2%E4%BC%98%E5%8C%96)
   -> linking to #用例 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E7%94%A8%E4%BE%8B)
   -> linking to #创建-eks-集群 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E5%88%9B%E5%BB%BA-eks-%E9%9B%86%E7%BE%A4)
   -> linking to #eks-插件 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#eks-%E6%8F%92%E4%BB%B6)
   -> linking to #配置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E9%85%8D%E7%BD%AE)
   -> linking to #用于节点扩展的-karpenter (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E7%94%A8%E4%BA%8E%E8%8A%82%E7%82%B9%E6%89%A9%E5%B1%95%E7%9A%84-karpenter)
   -> linking to #混合实例 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%B7%B7%E5%90%88%E5%AE%9E%E4%BE%8B)
   -> linking to #设置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E8%AE%BE%E7%BD%AE)
   -> linking to #配置步骤 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E9%85%8D%E7%BD%AE%E6%AD%A5%E9%AA%A4)
   -> linking to #部署 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E9%83%A8%E7%BD%B2)
   -> linking to #trino-coordinator-配置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#trino-coordinator-%E9%85%8D%E7%BD%AE)
   -> linking to #交换管理器配置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E4%BA%A4%E6%8D%A2%E7%AE%A1%E7%90%86%E5%99%A8%E9%85%8D%E7%BD%AE)
   -> linking to #trino-pod-资源请求与限制 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#trino-pod-%E8%B5%84%E6%BA%90%E8%AF%B7%E6%B1%82%E4%B8%8E%E9%99%90%E5%88%B6)
   -> linking to #worker-pod (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#worker-pod)
   -> linking to #coordinator-pod (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#coordinator-pod)
   -> linking to #此策略的好处 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%AD%A4%E7%AD%96%E7%95%A5%E7%9A%84%E5%A5%BD%E5%A4%84)
   -> linking to #自动扩展配置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E8%87%AA%E5%8A%A8%E6%89%A9%E5%B1%95%E9%85%8D%E7%BD%AE)
   -> linking to #文件缓存 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%96%87%E4%BB%B6%E7%BC%93%E5%AD%98)
   -> linking to #计算选择 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E8%AE%A1%E7%AE%97%E9%80%89%E6%8B%A9)
   -> linking to #网络规划 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E7%BD%91%E7%BB%9C%E8%A7%84%E5%88%92)
   -> linking to #vpc-cni-插件 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#vpc-cni-%E6%8F%92%E4%BB%B6)
   -> linking to #配置-vpc-cni-插件 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E9%85%8D%E7%BD%AE-vpc-cni-%E6%8F%92%E4%BB%B6)
   -> linking to #amazon-s3-作为主存储 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#amazon-s3-%E4%BD%9C%E4%B8%BA%E4%B8%BB%E5%AD%98%E5%82%A8)
   -> linking to #coordinator-和-worker-的-ebs-存储 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#coordinator-%E5%92%8C-worker-%E7%9A%84-ebs-%E5%AD%98%E5%82%A8)
   -> linking to #性能优化 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%80%A7%E8%83%BD%E4%BC%98%E5%8C%96)
   -> linking to #数据生命周期管理 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%95%B0%E6%8D%AE%E7%94%9F%E5%91%BD%E5%91%A8%E6%9C%9F%E7%AE%A1%E7%90%86)
   -> linking to #成本优化 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%88%90%E6%9C%AC%E4%BC%98%E5%8C%96)
   -> linking to #安全性和合规性 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E5%AE%89%E5%85%A8%E6%80%A7%E5%92%8C%E5%90%88%E8%A7%84%E6%80%A7)
   -> linking to #hive-连接器配置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#hive-%E8%BF%9E%E6%8E%A5%E5%99%A8%E9%85%8D%E7%BD%AE)
   -> linking to #hive-配置参数 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#hive-%E9%85%8D%E7%BD%AE%E5%8F%82%E6%95%B0)
   -> linking to #示例-hive-目录配置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E7%A4%BA%E4%BE%8B-hive-%E7%9B%AE%E5%BD%95%E9%85%8D%E7%BD%AE)
   -> linking to #metastore-配置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#metastore-%E9%85%8D%E7%BD%AE)
   -> linking to #身份验证 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E8%BA%AB%E4%BB%BD%E9%AA%8C%E8%AF%81)
   -> linking to #性能优化-1 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%80%A7%E8%83%BD%E4%BC%98%E5%8C%96-1)
   -> linking to #数据压缩 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%95%B0%E6%8D%AE%E5%8E%8B%E7%BC%A9)
   -> linking to #安全考虑 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E5%AE%89%E5%85%A8%E8%80%83%E8%99%91)
   -> linking to #iceberg-连接器配置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#iceberg-%E8%BF%9E%E6%8E%A5%E5%99%A8%E9%85%8D%E7%BD%AE)
   -> linking to #配置参数 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E9%85%8D%E7%BD%AE%E5%8F%82%E6%95%B0)
   -> linking to #示例-iceberg-目录配置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E7%A4%BA%E4%BE%8B-iceberg-%E7%9B%AE%E5%BD%95%E9%85%8D%E7%BD%AE)
   -> linking to #目录配置 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E7%9B%AE%E5%BD%95%E9%85%8D%E7%BD%AE)
   -> linking to #性能优化-2 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%80%A7%E8%83%BD%E4%BC%98%E5%8C%96-2)
   -> linking to #安全考虑-1 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E5%AE%89%E5%85%A8%E8%80%83%E8%99%91-1)
   -> linking to #指南 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%8C%87%E5%8D%97)
   -> linking to #内存管理 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E5%86%85%E5%AD%98%E7%AE%A1%E7%90%86)
   -> linking to #查询优化-1 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E6%9F%A5%E8%AF%A2%E4%BC%98%E5%8C%96-1)
   -> linking to #资源管理 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E8%B5%84%E6%BA%90%E7%AE%A1%E7%90%86)
   -> linking to #交换管理 (resolved as: /data-on-eks/zh/docs/bestpractices/analytics/trino-best-practices#%E4%BA%A4%E6%8D%A2%E7%AE%A1%E7%90%86)
- Broken anchor on source page path = /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-eks-karpenter:
   -> linking to #%E8%87%AA%E5%AE%9A%E4%B9%89%E6%8F%92%E4%BB%B6 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-eks-karpenter#%E8%87%AA%E5%AE%9A%E4%B9%89%E6%8F%92%E4%BB%B6)
   -> linking to #自定义插件 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-eks-karpenter#%E8%87%AA%E5%AE%9A%E4%B9%89%E6%8F%92%E4%BB%B6)
   -> linking to #先决条件 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-eks-karpenter#%E5%85%88%E5%86%B3%E6%9D%A1%E4%BB%B6)
   -> linking to #验证资源 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-eks-karpenter#%E9%AA%8C%E8%AF%81%E8%B5%84%E6%BA%90)
   -> linking to #先决条件-1 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-eks-karpenter#%E5%85%88%E5%86%B3%E6%9D%A1%E4%BB%B6-1)
- Broken anchor on source page path = /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-eks-spark-operator:
   -> linking to #先决条件 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-eks-spark-operator#%E5%85%88%E5%86%B3%E6%9D%A1%E4%BB%B6)
   -> linking to #部署 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-eks-spark-operator#%E9%83%A8%E7%BD%B2)
   -> linking to #验证资源 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-eks-spark-operator#%E9%AA%8C%E8%AF%81%E8%B5%84%E6%BA%90)
- Broken anchor on source page path = /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-spark-rapids:
   -> linking to #先决条件 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-spark-rapids#%E5%85%88%E5%86%B3%E6%9D%A1%E4%BB%B6)
   -> linking to #部署 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-spark-rapids#%E9%83%A8%E7%BD%B2)
   -> linking to #验证资源 (resolved as: /data-on-eks/zh/docs/blueprints/amazon-emr-on-eks/emr-spark-rapids#%E9%AA%8C%E8%AF%81%E8%B5%84%E6%BA%90)
- Broken anchor on source page path = /data-on-eks/zh/docs/blueprints/job-schedulers/self-managed-airflow:
   -> linking to #从-airflow-web-ui-创建-kubernetes-默认连接 (resolved as: /data-on-eks/zh/docs/blueprints/job-schedulers/self-managed-airflow#%E4%BB%8E-airflow-web-ui-%E5%88%9B%E5%BB%BA-kubernetes-%E9%BB%98%E8%AE%A4%E8%BF%9E%E6%8E%A5)
   -> linking to #执行示例-spark-作业-dag (resolved as: /data-on-eks/zh/docs/blueprints/job-schedulers/self-managed-airflow#%E6%89%A7%E8%A1%8C%E7%A4%BA%E4%BE%8B-spark-%E4%BD%9C%E4%B8%9A-dag)
- Broken anchor on source page path = /data-on-eks/zh/docs/blueprints/streaming-platforms/emr-eks-flink:
   -> linking to #先决条件 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/emr-eks-flink#%E5%85%88%E5%86%B3%E6%9D%A1%E4%BB%B6)
   -> linking to #部署 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/emr-eks-flink#%E9%83%A8%E7%BD%B2)
- Broken anchor on source page path = /data-on-eks/zh/docs/blueprints/streaming-platforms/emr-eks-stream:
   -> linking to #3-%E5%8F%AF%E9%80%89-%E5%90%91-emr-on-ec2-%E6%8F%90%E4%BA%A4%E6%AD%A5%E9%AA%A4 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/emr-eks-stream#3-%E5%8F%AF%E9%80%89-%E5%90%91-emr-on-ec2-%E6%8F%90%E4%BA%A4%E6%AD%A5%E9%AA%A4)
   -> linking to #1-%E5%8F%AF%E9%80%89-%E6%9E%84%E5%BB%BA%E8%87%AA%E5%AE%9A%E4%B9%89-docker-%E9%95%9C%E5%83%8F (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/emr-eks-stream#1-%E5%8F%AF%E9%80%89-%E6%9E%84%E5%BB%BA%E8%87%AA%E5%AE%9A%E4%B9%89-docker-%E9%95%9C%E5%83%8F)
- Broken anchor on source page path = /data-on-eks/zh/docs/blueprints/streaming-platforms/flink:
   -> linking to #先决条件 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/flink#%E5%85%88%E5%86%B3%E6%9D%A1%E4%BB%B6)
   -> linking to #部署 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/flink#%E9%83%A8%E7%BD%B2)
- Broken anchor on source page path = /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka:
   -> linking to #使用-ebs-作为持久存储后端的优势 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E4%BD%BF%E7%94%A8-ebs-%E4%BD%9C%E4%B8%BA%E6%8C%81%E4%B9%85%E5%AD%98%E5%82%A8%E5%90%8E%E7%AB%AF%E7%9A%84%E4%BC%98%E5%8A%BF)
   -> linking to #在-aws-上自管理-kafka-时应该使用什么-ebs-卷 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E5%9C%A8-aws-%E4%B8%8A%E8%87%AA%E7%AE%A1%E7%90%86-kafka-%E6%97%B6%E5%BA%94%E8%AF%A5%E4%BD%BF%E7%94%A8%E4%BB%80%E4%B9%88-ebs-%E5%8D%B7)
   -> linking to #出于性能原因使用-nvme-ssd-实例存储怎么样 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E5%87%BA%E4%BA%8E%E6%80%A7%E8%83%BD%E5%8E%9F%E5%9B%A0%E4%BD%BF%E7%94%A8-nvme-ssd-%E5%AE%9E%E4%BE%8B%E5%AD%98%E5%82%A8%E6%80%8E%E4%B9%88%E6%A0%B7)
   -> linking to #先决条件 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E5%85%88%E5%86%B3%E6%9D%A1%E4%BB%B6)
   -> linking to #部署 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E9%83%A8%E7%BD%B2)
   -> linking to #验证部署 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E9%AA%8C%E8%AF%81%E9%83%A8%E7%BD%B2)
   -> linking to #创建-kube-配置 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E5%88%9B%E5%BB%BA-kube-%E9%85%8D%E7%BD%AE)
   -> linking to #获取节点 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E8%8E%B7%E5%8F%96%E8%8A%82%E7%82%B9)
   -> linking to #部署-kafka-集群清单 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E9%83%A8%E7%BD%B2-kafka-%E9%9B%86%E7%BE%A4%E6%B8%85%E5%8D%95)
   -> linking to #检查-karpenter-配置的节点 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E6%A3%80%E6%9F%A5-karpenter-%E9%85%8D%E7%BD%AE%E7%9A%84%E8%8A%82%E7%82%B9)
   -> linking to #验证-kafka-代理和控制器 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E9%AA%8C%E8%AF%81-kafka-%E4%BB%A3%E7%90%86%E5%92%8C%E6%8E%A7%E5%88%B6%E5%99%A8)
   -> linking to #验证正在运行的-kafka-pod (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E9%AA%8C%E8%AF%81%E6%AD%A3%E5%9C%A8%E8%BF%90%E8%A1%8C%E7%9A%84-kafka-pod)
   -> linking to #创建-kafka-主题 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E5%88%9B%E5%BB%BA-kafka-%E4%B8%BB%E9%A2%98)
   -> linking to #执行示例-kafka-生产者 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E6%89%A7%E8%A1%8C%E7%A4%BA%E4%BE%8B-kafka-%E7%94%9F%E4%BA%A7%E8%80%85)
   -> linking to #执行示例-kafka-消费者 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E6%89%A7%E8%A1%8C%E7%A4%BA%E4%BE%8B-kafka-%E6%B6%88%E8%B4%B9%E8%80%85)
   -> linking to #kafka-生产者和消费者输出 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#kafka-%E7%94%9F%E4%BA%A7%E8%80%85%E5%92%8C%E6%B6%88%E8%B4%B9%E8%80%85%E8%BE%93%E5%87%BA)
   -> linking to #登录-grafana (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E7%99%BB%E5%BD%95-grafana)
   -> linking to #打开-strimzi-kafka-仪表板 (resolved as: /data-on-eks/zh/docs/blueprints/streaming-platforms/kafka#%E6%89%93%E5%BC%80-strimzi-kafka-%E4%BB%AA%E8%A1%A8%E6%9D%BF)
- Broken anchor on source page path = /data-on-eks/zh/docs/resources/mountpoint-s3-for-spark:
   -> linking to #先决条件 (resolved as: /data-on-eks/zh/docs/resources/mountpoint-s3-for-spark#%E5%85%88%E5%86%B3%E6%9D%A1%E4%BB%B6)
   -> linking to #部署 (resolved as: /data-on-eks/zh/docs/resources/mountpoint-s3-for-spark#%E9%83%A8%E7%BD%B2)

@github-actions GitHub Actions
Copy link
Contributor

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Oct 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

stale

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@hitsub2 @nabuskey @vara-bonthu