cert-manager: removing and preventing 'alternate' versions of Helm charts

[munnerz]

As posted over on the Helm Hub repository, we've found that a number of users have published 'alternate' versions of our Helm chart. This can cause confusion and potentially big issues around upgrade for end-users.

Full details can be found in helm/hub#402 😄

Wondering if there's any recourse to do the same here (although I appreciate/understand that you only pull these repos in because Helm Hub also pulls them in 😄)

[ankushchadha]

Thanks, @munnerz for submitting this issue. This concern is valid. Having the correct chart listed as a featured chart does encourage users to opt for the correct chart.

I think, in addition, we should implement a certified badge capability that allows primary authors to back a certain chart. This will result in certified badges to be displayed on the search results and chart page (info panel). Behind the scenes, we either have to detect forks or just go ahead with the recommendation of the primary author. When to apply a badge on what will be a problem though. At times the metadata such as popularity, security issues, etc helps consumers to make a better decision, but given that ChartCenter just started, it's going to take some time to build the popularity data (such as download count)

CC @Dattax @rimusz @elioengcomp WDYT?