You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/02/20 18:25:00 UTC

[jira] [Commented] (KNOX-3257) Update knox image creatation so that we do not need escalated privileges in helm install

    [ https://issues.apache.org/jira/browse/KNOX-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059956#comment-18059956 ] 

ASF subversion and git services commented on KNOX-3257:
-------------------------------------------------------

Commit 56e0f31ef021d5c16d1f6a6601545d47872c2dba in knox's branch refs/heads/KNOX-3257 from Sandeep Moré
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=56e0f31ef ]

KNOX-3257 - Review changes


> Update knox image creatation so that we do not need escalated privileges in helm install  
> ------------------------------------------------------------------------------------------
>
>                 Key: KNOX-3257
>                 URL: https://issues.apache.org/jira/browse/KNOX-3257
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: docker
>            Reporter: Sandeep More
>            Assignee: Sandeep More
>            Priority: Major
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Currently knox docker images are created such that only knox user has access to it's fil;es and directories. There are times when helm operations want to update the keystore, to add certs specifically, such operations need root privileges in helm (or use the exact knox UID which cannot be determined by helm container init). The proposed solution is to create a group "knox" with a specific GID and have all the knox specific dirs owned by this group. 
> Then in helm we use that GID to perform operations.  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)