FairwindsOps/nova

Nova unable to flag deprecated Helm charts

kimschles opened this issue · 3 comments

What happened?

While working on a blog post about Nova, I wasn't able to get the tool to flag 2 deprecated charts.

I installed nginx-ingress and kube2iam from the deprecated helm chart repo, but nova is still reporting that these are not deprecated:

Release Name      Installed    Latest    Old      Deprecated
============      =========    ======    ===      ==========
kube2iam          2.5.3        2.6.0     true     false
metrics-server    3.8.0        3.8.2     true     false
nginx-ingress     1.41.0       1.41.2    true     false
vpa               1.4.0        1.4.0     false    false

I'm running Nova v3.2.0.

What did you expect to happen?

I expect Nova identify charts with deprecated: true in their Chart.yaml as deprecated.

How can we reproduce this?

kubewatch is a deprecated chart.

Install it with the command:

helm repo add bitnami https://charts.bitnami.com/bitnami
helm install my-release bitnami/kubewatch

Then, run nova find and you will see

Release Name             Installed    Latest    Old      Deprecated
============             =========    ======    ===      ==========
kubewatch                3.3.4        3.3.4    false    false

Per @sudermanjr, the artifacthub functionality broke the Deprecated function.

If you disable artifact hub, and specify the repository directly, it gets the field to flip:

nova find --poll-artifacthub=false --url=https://charts.bitnami.com/bitnami

Release Name    Installed    Latest    Old      Deprecated
============    =========    ======    ===      ==========
kubewatch       3.3.4        3.3.4     false    true

Version

3.2.0

Search

  • I did search for other open and closed issues before opening this.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Additional context

No response

If we were able to get this feature added to helm, we could eliminate this issue.

deiga commented

@sudermanjr Since that feature has been added, is this issue still valid?

Unfortunately that feature has not been added to helm. The HIP was approved, however we are still waiting on helm/helm#11378 to be approved before this can happen.