You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "Gallardot (via GitHub)" <gi...@apache.org> on 2023/10/07 08:35:27 UTC

[I] [Feature][Helm] Supports deploying only partial components. [dolphinscheduler]

Gallardot opened a new issue, #14984:
URL: https://github.com/apache/dolphinscheduler/issues/14984

   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
   
   
   ### Description
   
   During installation via Helm, it is possible to deploy different worker images to meet various use case scenarios. 
   For example:
   1. when a cluster has both CPU and GPU servers, different worker images are required. 
   2. Multiple tenants can deploy and use different workers separately. 
   3. Deploying components separately can reduce the impact on maintenance.
   
   Users can deploy in the following manner:
   ```bash
   #1. Deploy master, api-server, and alert-server.
   helm install ds dolphinscheduler -n ds --set master.enabled=true  --set api.enabled=true --set alert.enabled=true --set worker.enabled=false
   #2. Deploy worker for CPU servers.
   helm install ds-cpu-worker dolphinscheduler -n ds --set master.enabled=false  --set api.enabled=false --set alert.enabled=false --set worker.enabled=true --set image.tag=3.2.0 --set worker.nodeSelector.cpu="x86"
   #3. Deploy worker for GPU servers.
   helm install ds-gpu-worker dolphinscheduler -n ds --set master.enabled=false  --set api.enabled=false --set alert.enabled=false --set worker.enabled=true --set image.tag=3.2.0-GPU --set worker.nodeSelector.gpu="a100"
   ```
   
   Note: for compatibility, by default, all components are installed and deployed.
   
   ### Use case
   
   as mentioned above
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature][Helm] Supports deploying only partial components. [dolphinscheduler]

Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS closed issue #14984: [Feature][Helm] Supports deploying only partial components.
URL: https://github.com/apache/dolphinscheduler/issues/14984


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org