You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2022/11/02 01:57:00 UTC
[jira] [Commented] (YUNIKORN-1359) Bring-your-own config
[ https://issues.apache.org/jira/browse/YUNIKORN-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627412#comment-17627412 ]
Craig Condit commented on YUNIKORN-1359:
----------------------------------------
[~derektbrown] please see the design doc in YUNIKORN-1221, which is our updated configuration design. Since we will be using a configmap for all configuration moving forward (and not just the core config), we need an alternative mechanism to implement disabling configmap generation.
I would recommend adding a new Helm attribute:
* {*}enableConfigMap{*}: *true* | false (default true for backwards compatibility)
* When true, ConfigMap will be generated as part of the Helm deployment (as it is currently). When false, no ConfigMap will be generated at all as part of Helm deployment.
> Bring-your-own config
> ---------------------
>
> Key: YUNIKORN-1359
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1359
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: deployment
> Reporter: Derek Brown
> Assignee: Derek Brown
> Priority: Trivial
> Labels: pull-request-available
>
> We want to be able to specify our own ConfigMap. To do this, we need to be able to disable the creation of the default ConfigMap.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org