[
https://issues.apache.org/jira/browse/YUNIKORN-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627471#comment-17627471
]
Wilfred Spiegelenburg commented on YUNIKORN-1359:
-------------------------------------------------
This still leaves open the point that we currently will not start without the
ConfigMap present. The proposal to use a default configuration if the ConfigMap
is not found, part of the [redesigned
config|https://docs.google.com/document/d/1HVs__g7jYmOHgEEp1Zl0Xii0T9_ztuT3-K1u0wAyHDY/edit#heading=h.frygiv1cq9j5],
has a major impact.
As an example existing pods waiting in a cluster could be scheduled while they
should not be as they are above a quota. Starting with a default config without
making this really clear or even failing it unless a certain flag is set needs
to be looked into.
We can change the helm side to not generate and deploy a ConfigMap but we need
to be really clear about the consequences of that flag. This needs to be bullet
proof and assuming that everyone knows exactly what they are doing is not good
enough.
> 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]
