bitflicker64 commented on PR #3132:
URL: https://github.com/apache/hugegraph/pull/3132#issuecomment-5315260141

   ### Checkpoint (2026-08-17)
   
   Re-validated this PR head (`84c56fc7`) on Kubernetes against the published 
Docker Hub images:
   
   - `hugegraph/pd:latest`
   - `hugegraph/store:latest`
   - `hugegraph/server:latest`
   - `hugegraph/hubble:latest`
   
   **Topology:** 3 PD + 3 Store + 3 Server + 1 Hubble, authentication enabled 
(chart defaults), Hubble in `pd` mode.
   
   **Results**
   - All 10 Pods Ready with zero restarts; `helm test` passed.
   - Protected APIs return 401 without credentials / with a wrong password; 
chart-managed admin Secret and `/auth/login` JWT succeed.
   - The same JWT is accepted by all three Server Pods (shared 
`auth.token_secret`).
   - Every Server Pod renders `usePD=true`, the three PD peers, 
`server.urls_to_pd`, `server.deploy_in_k8s=true`, and `StandardAuthenticator` 
with `auth.admin_pa` from the chart Secret.
   - REST create / read / update / delete on an HStore graph succeeded.
   - Hubble login (chart admin Secret), PD discovery of graph spaces/graphs, 
vertex create, and `gremlin-query` succeeded.
   - Loaded a sample `demo` graph (~100 vertices / ~100 edges) and queried it 
through Hubble.
   
   **Notes (expected)**
   - Hubble cluster overview lists a single Server endpoint because all Server 
replicas register the shared client Service URL with PD.
   - Overview may show an aggregate PD status of UNKNOWN while individual PD 
members remain UP.
   
   Still pending before leaving draft: the full multi-node upgrade / 
replacement / failover lifecycle matrix, and pinning image tags when the next 
release exists.


-- 
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