[ 
https://issues.apache.org/jira/browse/RANGER-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek Kumar updated RANGER-5401:
-----------------------------------
    Description: 
To leverage existing docker images and support both docker and Kubernetes based 
deployments, it is important to keep application configs (eg: 
install.properties) outside the image(Dockerfile). 

The configs can be removed from the image layer and be driven from:
1. Volumes in docker-compose for docker based deployments.
2. ConfigMaps in helm-charts for Kubernetes based deployments.

The jira aims to update all ranger-plugin docker images to support this.


  was:
To leverage existing docker images and support both docker and Kubernetes based 
deployments, it is important to keep application configs (eg: 
install.properties) outside the image(Dockerfile). 

The configs can be removed from the image layer and be driven from:
1. Volumes in docker-compose for docker based deployments.
2. ConfigMaps in helm-charts for Kubernetes based deployments.

The jira aims to update all ranger-server docker images to support this.



> [docker] Use Volume Mounts for ranger-plugin configs
> ----------------------------------------------------
>
>                 Key: RANGER-5401
>                 URL: https://issues.apache.org/jira/browse/RANGER-5401
>             Project: Ranger
>          Issue Type: Improvement
>          Components: docker, Ranger
>            Reporter: Abhishek Kumar
>            Assignee: Abhishek Kumar
>            Priority: Major
>
> To leverage existing docker images and support both docker and Kubernetes 
> based deployments, it is important to keep application configs (eg: 
> install.properties) outside the image(Dockerfile). 
> The configs can be removed from the image layer and be driven from:
> 1. Volumes in docker-compose for docker based deployments.
> 2. ConfigMaps in helm-charts for Kubernetes based deployments.
> The jira aims to update all ranger-plugin docker images to support this.



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

Reply via email to