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/10/31 14:35:00 UTC
[jira] [Commented] (YUNIKORN-1371) Helm: Implement config migration from legacy configuration
[ https://issues.apache.org/jira/browse/YUNIKORN-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626619#comment-17626619 ]
Craig Condit commented on YUNIKORN-1371:
----------------------------------------
FYI, this needs to wait until the remainder of the subtasks for YUNIKORN-1221 are finished. Bsaed on how things go with the other tasks, this may change significantly.
> Helm: Implement config migration from legacy configuration
> ----------------------------------------------------------
>
> Key: YUNIKORN-1371
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1371
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: release
> Reporter: Craig Condit
> Assignee: Ryan Lo
> Priority: Major
>
> We need to update our helm charts to support the new configuration options outlined in YUNIKORN-1221 and mark the legacy configs as deprecated in our documentation:
> * {*}generateLegacyConfig{*}: *true* | false
> *
> ** When true, all legacy Helm variables will map to legacy configuration as before
> ** When false, legacy Helm variables will be *ignored* and the ConfigMap generated will be empty
> * {*}migrateLegacyConfig{*}: true | *false*
> ** When true, any generated ConfigMap will include legacy Helm variables mapped to new ConfigMap entries
> ** When false, legacy configuration variables will *not* be included in ConfigMap generation
--
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