bingquanzhao opened a new pull request, #4171:
URL: https://github.com/apache/doris-website/pull/4171

   ## Versions 
   
   - [x] dev
   - [x] 4.x
   - [x] 3.x
   - [ ] 2.1 or older (not covered by version/language sync gate)
   
   ## Languages
   
   - [x] Chinese
   - [x] English
   
   ## Docs Checklist
   
   - [x] Checked by AI
   - [ ] Test Cases Built
   - [ ] Updated required version and language counterparts, or explained why 
not
   - [ ] If only one language changed, confirmed whether source/translation 
counterparts need sync
   
   ## What changed
   
   The DOG Stack "Deployment" page mixed Docker Compose, Kubernetes and manual 
deployment. Its Kubernetes section installed `dogstack/dogstack` from 
`charts.velodb.io`, a chart that does not exist there (the repository only 
serves `ai-observe-stack` 0.1.0, and its TLS certificate expired on 2026-03-20).
   
   - **New page `observability/dogstack/kubernetes` (Deploy on Kubernetes).** 
Installs the two Helm charts from 
[ai-observe/ai-observe-stack](https://github.com/ai-observe/ai-observe-stack/tree/main/helm-charts):
 `ai-observe-stack` (OpenTelemetry gateway, Grafana with the Doris App plugin, 
and optionally Doris through the Doris Operator) and `dog-k8s-collector` 
(container logs, kubelet / node / cluster metrics, Kubernetes Events). Covers:
     - an existing Doris, including the requirement that the BE addresses 
registered in Doris and port 8040 be reachable from the gateway pods for Stream 
Load;
     - a chart-deployed Doris, with the settings in `prod.yaml` that must be 
adapted to the environment;
     - what the collector adds and when it can be skipped;
     - verification with SQL and an end-to-end JSON log example;
     - log parsing rules and presets, OTLP from applications, Prometheus 
scraping, multiple clusters;
     - production settings, upgrade, uninstall (PVCs, the `helm test` pod and 
the Doris Operator CRD that Helm leaves behind), and troubleshooting.
   - **`deployment.md` renamed to `docker.md` (Deploy with Docker Compose).** 
Fixes commands that were joined on one line, adds the existing-Doris mode, and 
states that the BE addresses registered in Doris must be reachable from the 
collector container.
   - **Navigation.** A "Deployment" category holds both pages in dev, 4.x and 
3.x, with the zh-CN label "部署". The old `…/observability/dogstack/deployment` 
URLs (dev, 4.x, 3.x, en and zh-CN) redirect to the Docker Compose page through 
the existing `createRedirects` index in `docusaurus.config.js`. No other page 
linked to the old URL.
   
   The DOG Stack pages are identical across dev, 4.x and 3.x, so all six copies 
of each page are updated and identical. English and Chinese have the same 
sections, tables, admonitions and code blocks.
   
   ## Testing
   
   Both pages were run end to end, command by command:
   
   - **Kubernetes:** on a single-node k3s cluster with Helm 3.19 and no Helm 
repositories added:
     - chart-deployed Doris with the chart's own Doris Operator 1.6.1, and an 
existing Doris;
     - for each: `helm test`, Grafana login and dashboards, collector install, 
the verification SQL and the JSON end-to-end example;
     - a `helm upgrade` with a preset rule, checked offline first with 
`hack/test-rule.sh`;
     - uninstall with the documented cleanup commands.
   - **Troubleshooting:** the missing-zoneinfo row was reproduced on the same 
cluster.
   - **Docker Compose:** both modes on a Linux host; host ports were remapped 
with a compose override because the host already used 3000 and 4317.
   - **Local site:** local dev server (`DOCS_VERSIONS=4.x`), en and zh-CN: both 
pages compile and render. A full-width comma right after a bare URL broke MDX 
compilation of the zh-CN pages; those URLs now use `<…>` autolinks.
   
   Issues found during the run were fixed in the charts first 
(ai-observe/ai-observe-stack#17 and #18), so the pages describe the current 
`main`.
   
   Not run locally: a full `yarn build` of all versions and locales.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to