[
https://issues.apache.org/jira/browse/YUNIKORN-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567208#comment-17567208
]
Wilfred Spiegelenburg commented on YUNIKORN-1261:
-------------------------------------------------
Helm does a 3 way merge in v3. If the configmap has been updated in the cluster
the value from the cluster might be considered more recent and the "new" value
from the chart could be ignored. We have no control over what helm does during
the upgrade call. Unless the chart we have breaks helm's processing.
Can you show the base chart and the updated chart? (sanitised if needed) so we
can see the difference between the two?
> Helm upgrade does not detect changes in ConfigMap
> -------------------------------------------------
>
> Key: YUNIKORN-1261
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1261
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: release
> Affects Versions: 1.0.0
> Reporter: Chaoran Yu
> Priority: Major
>
> For an existing Helm release of YuniKorn, when there's a change in the
> ConfigMap (e.g. new queue configurations) and the release is upgraded using
> the "helm upgrade" command, the ConfigMap doesn't get updated
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
