rickchengx opened a new pull request, #11508:
URL: https://github.com/apache/dolphinscheduler/pull/11508

   
   
   <!--Thanks very much for contributing to Apache DolphinScheduler. Please 
review 
https://dolphinscheduler.apache.org/en-us/community/development/pull-request.html
 before opening a pull request.-->
   
   
   ## Purpose of the pull request
   
   Use `configmap` to mount the configuration files of each server so that user 
can easily modify the configuration of each server when deploying 
Dolphinscheduler in the k8s cluster through `Helm`.
   
   Ref:
   https://kubernetes.io/docs/concepts/configuration/configmap/
   https://helm.sh/docs/chart_template_guide/accessing_files/
   
   
   For example, if the user wants to change the configuration (E.g., the `root 
directory` of `zookeeper` in `application.yaml`, or the `log.base` in 
`log.base` in `logback-spring.yaml`, or `resource.storage.type` in 
`common.properties`), he can directly do the modification in 
`deploy/kubernetes/dolphinscheduler/conf/<server>/<configuration file>`.
   
   Take `master-server` as an example, k8s will automatically mount the 
configmap (4 configuration files in 
`deploy/kubernetes/dolphinscheduler/conf/master-server`) to 
`/opt/dolphinscheduler/conf` in the container.
   
   
   ## Brief change log
   
   <!--*(for example:)*
     - *Add maven-checkstyle-plugin to root pom.xml*
   -->
   ## Verify this pull request
   
   <!--*(Please pick either of the following options)*-->
   
   Manually verified the change by testing locally.
   
   `/opt/dolphinscheduler/conf` in the container is mounted.
   
   <img width="687" alt="image" 
src="https://user-images.githubusercontent.com/38122586/184853253-d9c3ddbf-aeb8-4b46-a327-09296628f8e3.png";>
   
   


-- 
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]

Reply via email to