aicam opened a new pull request, #8778: URL: https://github.com/apache/texera/pull/8778
### What changes were proposed in this PR? Documents in `SECURITY.md` that some of Texera's security features rely on Kubernetes, so the security model is only fully provided by the Kubernetes deployment: - New section, "Deployment Modes and Security Coverage". The Kubernetes deployment (Helm chart under `bin/k8s`) is the only mode that provides the full security model: requests go through the gateway, which enforces access control, and computing units are isolated from each other. Local JVM deployments (`bin/local-dev.sh` or running the services directly) and single-node Docker Compose deployments (`bin/single-node`) lack that gateway and isolation, so their security is not guaranteed. They are meant for development, evaluation, and single-user or fully trusted teams. - "What is NOT Guaranteed" gains a bullet for local JVM and Docker Compose deployments. - "What are NOT Security Issues" gains an entry: access-control gaps that exist only in those modes are out of scope, unless they can also be reproduced on Kubernetes. - Local computing units are now described as "fully-trusted-team use" instead of "small team use", and "Last Updated" is September 2026. ### Any related issues, documentation, discussions? None. ### How was this PR tested? Docs-only change; no code touched. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 5.5) 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
