bitflicker64 opened a new issue, #3211:
URL: https://github.com/apache/hugegraph/issues/3211

   ## Feature Description (功能描述)
   
   The published `hugegraph/pd`, `hugegraph/store` and `hugegraph/server` 
images all run their Java process as root: none of the three declares a `USER`, 
checked against the current `latest` image configs on Docker Hub (registry 
config blob, `.config.User` empty on all three, 2026-09-17).
   
   Why it matters on Kubernetes:
   
   1. A namespace under the `restricted` Pod Security Standard rejects these 
pods outright (`runAsNonRoot != true`).
   2. The Helm chart in #3132 cannot set `runAsNonRoot: true` or 
`readOnlyRootFilesystem: true` as defaults; it documents this in its 
Limitations and ships the remaining hardening it can 
(`allowPrivilegeEscalation: false`, `capabilities.drop: [ALL]`, 
`seccompProfile: RuntimeDefault`).
   3. Security scanners (kube-score, polaris, kubescape) flag every workload 
for it, which any adopter evaluating the chart sees on day one; the 2026-09-10 
chart test campaign recorded it as a failing kubescape NSA control on both 
branches.
   
   Proposal:
   
   - Create a fixed-UID user in each Dockerfile (the toolchain's Hubble image 
can follow the same pattern later) and `chown` the data and log directories to 
it.
   - Declare `USER` in the image and keep the entrypoints from writing outside 
the data, log and temp directories, so `readOnlyRootFilesystem` becomes 
possible as a follow-up.
   - Ship it in a minor release with an upgrade note: existing PVC data written 
as root needs a one-time `chown`, or an initContainer / `fsGroup` note in the 
chart.
   
   The chart side is ready to adopt this the release it lands: 
`podSecurityContext` and `securityContext` are fully configurable per component 
today, so only the defaults would change.
   


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

Reply via email to