[GitHub] [yunikorn-release] DerekTBrown commented on pull request #111: [YUNIKORN-1359] Bring-your-own ConfigMap

[GitBox <gi...@apache.org>]

DerekTBrown commented on PR #111:
URL: https://github.com/apache/yunikorn-release/pull/111#issuecomment-1281724817

   > How are you handling the fact that we cannot start without a configuration? We fail and exit if we cannot read the config. It would fail the helm deployment. That means the config map must be there before you deploy.
   
   In our case the `ConfigMap` will already be present when we deploy YuniKorn. 
   
   > We also already have the option to bring your [own config map](https://yunikorn.apache.org/docs/next/user_guide/queue_config#configuration) if you want.
   
   I am not quite sure what you are referring to? This section of the documentation describes the ability to use a different `.yaml` file for configuration. This doesn't solve the "bring your own" configuration problem, because the user would still need to mount the `ConfigMap` to the `Deployment` somehow, which requires modifying the official chart.
   


-- 
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: dev-unsubscribe@yunikorn.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org