Repository navigation
Conversation
bitflicker64
left a comment
There was a problem hiding this comment.
Blocking: no. Summary: Vermeer, RAG, bootstrap-record, Text2GQL key, Store lifecycle and Vermeer version claims match the chart, Hubble, Store and Vermeer sources on master, and the install commands render as described. Three small accuracy and maintainability gaps remain.
…button label, drop local temp path
bitflicker64
left a comment
There was a problem hiding this comment.
Blocking: no. Score: 9/10. Summary: Vermeer, RAG, bootstrap-record, Text2GQL key, Store lifecycle and NetworkPolicy claims match the chart, Hubble, Store and Vermeer sources on master, and both topology installs render as written. The storeReplicas, Test saved connection and evidence-path comments from the earlier head are resolved.
imbajin
left a comment
There was a problem hiding this comment.
Score: 7.0/10 · Confidence: medium
Blocking: yes
Summary
The volume repair instructions can restore the normal policy before OnDelete Store Pods have applied the recursive repair, leaving inaccessible files on their PVCs.
Evidence
The cluster preset sets Store to OnDelete; the new verification checks image names only, which can already match while the running Pod still uses the old security context.
Validation notes
Validated against the documentation and chart source; no live upgrade or recovery exercise was performed.
…ing OnRootMismatch
bitflicker64
left a comment
There was a problem hiding this comment.
Blocking: no. Summary: The Vermeer, RAG, bootstrap-record, fsGroup repair, Text2GQL key, Store lifecycle and NetworkPolicy claims match the chart, Hubble, Store and Vermeer sources on master, all install commands render as written, and the four earlier comments are fixed at this head. One Chinese cross-page link points to a fragment that does not exist.
imbajin
left a comment
There was a problem hiding this comment.
Score: 8.2/10 · Confidence: high
Blocking: no
Summary
The existing Chinese Store rollout link issue remains: operators following volume repair cannot jump to the controlled replacement procedure. The previous OnDelete repair finding is addressed.
Evidence
The target heading declares a different explicit fragment; the current recovery steps now require one-at-a-time replacements and verification of Always and shard recovery.
Validation notes
Reviewed documentation and chart sources; did not exercise a live cluster upgrade, volume recovery, or browser navigation.
…s bootstrap hygiene
bitflicker64
left a comment
There was a problem hiding this comment.
Blocking: no. Summary: The Store rollout split, Vermeer, RAG, Text2GQL key, bootstrap-record and NetworkPolicy claims match the chart, Hubble and Vermeer sources on master, and the install commands render as written. The values-hygiene sentence added at this head names a chart key that does not exist.
|
|
||
| The following are **fresh installation** choices. For an existing release, use `helm upgrade` with its complete reviewed values. | ||
| Older saved values can omit new component defaults; | ||
| export `helm get values hugegraph -n hugegraph --all -o yaml` to a private file, remove completed one-time initialization flags (such as `bootstrap.enable`), review it, then supply it with `-f` without `--reuse-values`. |
There was a problem hiding this comment.
Minor: the chart never had bootstrap.enable; saved values carry the legacy opt-in bootstrap.enabled, which values.schema.json rejects, and the operations page already calls it that. Name bootstrap.enabled as the legacy key to remove, here and in content/cn/docs/quickstart/hugegraph/hugegraph-helm.md.
Purpose of the PR
Update the bilingual Helm deployment and operations guides for the integrated Hubble, Vermeer and optional GraphRAG chart. The guides now explain persistent bootstrap settings, credentials and recovery paths alongside the steps users execute.
Validation: strict build and independent artifact/link checks passed. The current chart ran in a minimal authenticated Kind deployment: five components Ready, five PVCs Bound, installation and test hooks passed, and five Hubble-to-Vermeer algorithms completed with paged results. Chart rendering/lint/unit checks and desktop/mobile interactions passed.
The single-node run does not establish HA or recovery acceptance. RAG configuration was rendered without connecting a live model. Runtime image identities and six shared screenshots are recorded in the fixture.
Dependent guides are separated into Computing #71 and AI #74, both based on this branch. Merge this deployment foundation before retargeting those guides to master.