Helm App Upgrade: Use more fields when trying to find the correct matching chart for an app #11679
Labels
kind/enhancement
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
Milestone
EPIC: #11465
For Helm Apps, we attempt to find the chart for the app and then look to see if upgrades are available - if so, we indicate this to the user. A chart may exist in two (or more) Helm repositories. At the moment, we will just chose the first one, which means we might show an upgrade that the user probably doesn't want to make.
We should do a better job of finding the matching chart.
For reference, see: https://github.com/rancher/dashboard/blob/master/shell/models/catalog.cattle.io.app.js#L50
The store has a getter
catalog/chart
() - I suggest we add a new gettercatalog/matchingCharts
or alike that returns all of hte matching charts.The code here - https://github.com/rancher/dashboard/blob/master/shell/models/catalog.cattle.io.app.js#L50 - should use that new getter AND if there are multiple charts returned, it should check the following additional chart metadata properties to get a better match if possible:
If it finds a better match it should return that one - otherwise it should return the first, as it does today.
The text was updated successfully, but these errors were encountered: