tanishqgandhi1908 opened a new issue, #8450: URL: https://github.com/apache/texera/issues/8450
Backend. A `cu_image` table, an admin-only API to register, refresh, list and remove images, and a Kubernetes job that validates a reference and resolves its digest. Validation reads only the manifest and config blob, so a misspelled, private or non-Texera image is refused in seconds. The digest is recorded and is what units are started from. A curated image is supplied by an administrator and reviewed by nobody, so units started from one are pinned to a non-root user with no privilege escalation and no capabilities. The deployment's own image is untouched. **Done when** an admin can register a reference over the API, it reaches `READY` with a pinned digest, a bad one reaches `FAILED` with a readable reason, and a computing unit can be created from a ready image. Part of #8448 -- 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]
