[
https://issues.apache.org/jira/browse/KNOX-3257?focusedWorklogId=1006368&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1006368
]
ASF GitHub Bot logged work on KNOX-3257:
----------------------------------------
Author: ASF GitHub Bot
Created on: 20/Feb/26 12:37
Start Date: 20/Feb/26 12:37
Worklog Time Spent: 10m
Work Description: moresandeep opened a new pull request, #1151:
URL: https://github.com/apache/knox/pull/1151
[KNOX-3257](https://issues.apache.org/jira/browse/KNOX-3257) - Update knox
image creatation so that we do not need escalated privileges in helm install
## What changes were proposed in this pull request?
Update Knox docker file to
1. import commonly used certs
2. fix knox directories
## How was this patch tested?
This patch was tested on a local kind cluster.
Issue Time Tracking
-------------------
Worklog Id: (was: 1006368)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 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)
