bitflicker64 commented on PR #3132: URL: https://github.com/apache/hugegraph/pull/3132#issuecomment-5388153545
**Checkpoint (2026-08-23)** Since the 2026-08-17 checkpoint: - Ran a second full campaign on Kind (static gates, install, fault scenarios, upgrade path; details in the updated description). It exposed a first-install race in PD's IP allowlist: with parallel StatefulSet bring-up, a PD can resolve its peer allowlist before peer DNS exists, freeze a partial list, and wedge the install when it blocks the elected leader — one of two installs failed, with `Could not resolve allowlist entry` and `Blocked connection from <ip>` as the signatures. - Landed a chart-side mitigation: a `wait-for-pd-dns` init container gates PD start until every peer name resolves. With it, two of two installs deployed with zero allowlist errors on every PD. Runtime pod-IP churn remains image-side and is documented under Limitations; the gate will be revisited once the PD-side allowlist change under discussion lands. - Hardening in the same pass: explicit `updateStrategy` and PVC retention on PD/Store, a `checksum/auth` annotation so `existingSecret` rotation rolls Server, and NOTES/README fixes. - Upgrade path validated with marker data: PD and Server roll once as documented, Store does not; the documented post-roll remediation verified to converge cleanly. Secret switch and rotation both roll Server. Single-node preset validated. - The legacy `--reuse-values` CI guard caught one regression during this work (`pd.waitImage` briefly schema-required); fixed, and `lint-and-render` is green on the current head. Still before un-drafting: the open `/v1/health` quorum-signal thread (gating on `/v1/members` currently requires PD REST auth that current builds reject, so the signal choice is pending the PD-side direction), #3159, and release-tag pinning. -- 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]
