[
https://issues.apache.org/jira/browse/YUNIKORN-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634615#comment-17634615
]
Craig Condit edited comment on YUNIKORN-1359 at 11/16/22 2:59 AM:
------------------------------------------------------------------
Given the changes that are now landing in YUNIKORN-1221, I don't think we need
this any more. From the latest design doc:
{quote}We will use two ConfigMaps to configure YuniKorn:
* yunikorn-defaults
** This will be a new ConfigMap written by Helm; it will contain only values
explicitly configured by an administrator via Helm variables.
* yunikorn-configs
** This ConfigMap will contain overrides for yunikorn-defaults. It was
previously a Helm hook in previous YuniKorn releases; it will no longer be
managed by Helm and may be updated freely by third-party tools.
The effective configuration will be the combination of both yunikorn-defaults
and yunikorn-configs, with yunikorn-configs taking precedence.
Neither ConfigMap (even the existing one) is required for proper functionality.
In the case where a ConfigMap does not exist, we will use compiled-in defaults
for all options. This enables bootstrapping in a variety of environments,
including local development mode, as the ConfigMap need not exist to bring the
scheduler components up. Future configuration options should be set via the
ConfigMap exclusively.
{quote}
[~derektbrown] will this meet your needs? I think you can simply write out
yunikorn-configs yourself, and ignore yunikorn-defaults (which will be
effectively empty).
was (Author: ccondit):
Given the changes that are now landing in YUNIKORN-1221, I don't think we need
this any more. From the latest design doc:
{quote}We will use two ConfigMaps to configure YuniKorn:
* yunikorn-defaults
* This will be a new ConfigMap written by Helm; it will contain only values
explicitly configured by an administrator via Helm variables.
* yunikorn-configs
* This ConfigMap will contain overrides for yunikorn-defaults. It was
previously a Helm hook in previous YuniKorn releases; it will no longer be
managed by Helm and may be updated freely by third-party tools.
The effective configuration will be the combination of both yunikorn-defaults
and yunikorn-configs, with yunikorn-configs taking precedence.
Neither ConfigMap (even the existing one) is required for proper functionality.
In the case where a ConfigMap does not exist, we will use compiled-in defaults
for all options. This enables bootstrapping in a variety of environments,
including local development mode, as the ConfigMap need not exist to bring the
scheduler components up. Future configuration options should be set via the
ConfigMap exclusively.
{quote}
[~derektbrown] will this meet your needs? I think you can simply write out
yunikorn-configs yourself, and ignore yunikorn-defaults (which will be
effectively empty).
> 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: [email protected]
For additional commands, e-mail: [email protected]
