bitflicker64 commented on PR #3132: URL: https://github.com/apache/hugegraph/pull/3132#issuecomment-5550454292
Status 2026-09-05. This chart was tested against images that carry #3185, #3187 and #3189, built from the hugegraph/hugegraph tag `helm-dev-20260905` (`6ec19838`); the validation record in the description has the numbers, and each of the three PRs has a comment with its own results. New on the branch: `0a50f6fe` adds the PD REST secret wiring (`pd.auth`, a kept release-pd-auth Secret, consumed by PD, the Server storage wait and Hubble). Without it the chart cannot start PD images that include #3189; older images ignore the variables. Measured: upgrade to #3189 images in 175 s, the 57-request credential matrix answers 401 or 200 as designed, Hubble lists 3/3/3. Templates stay byte-identical with the testing branch, 58 unit tests. Once #3185, #3187 and #3189 are merged and a 1.8.0 image exists, this PR still needs one pass: 1. Values: flip `pd.readinessPath` and `store.waitPath` to `/v1/ready` and set `HG_SERVER_STARTUP_TIMEOUT_S` by default from the Server startup probe budget, in the same commit as the image tag pin; drop the two TODO comments in values.yaml. 2. README: rewrite the Limitations bullets on PD REST auth (1.7.0 name-only check against 1.8.0 password check) and on `/v1/health` against `/v1/ready` as the behaviour of pre-1.8.0 images. The Chart Details bullet on the PD secret and the Disaster Recovery commands already assume 1.8.0 and stay. 3. This description: the at-a-glance paragraph, the checklist items for the two flips, and the validation record. 4. Re-run the fault battery on the pinned images (follower and leader crash, Store loss, partition, PVC reattach, rolling restart under load, upgrade path from the last 0.1.x to the release chart version). Nothing in the campaign failed in a way the chart could fix; the one open image-side note (a 9.8 s stall in `/v1/ready` during an election) is on #3185. -- 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]
