FairwindsOps/pluto

Detect-files not finding helm chart when path is the root of the chart

ndlanier opened this issue · 2 comments

What happened?

Running pluto detect-files -d ./chart-repo/myexamplechart/ sees no deprecated or removed apiVersions. But it sees it when we run it from the root directory of the repo. I have manually specified the ingress template for the chart uses v1beta which is removed in kube 1.22

pluto detect-files -d ./
NAME                        KIND      VERSION              REPLACEMENT            REMOVED   DEPRECATED  
client-portal-web-ing       Ingress   extensions/v1beta1   networking.k8s.io/v1   true      true        
client-portal-web-com-ing   Ingress   extensions/v1beta1   networking.k8s.io/v1   true      true        
client-portal-web-ing       Ingress   extensions/v1beta1   networking.k8s.io/v1   true      true        
client-portal-web-com-ing   Ingress   extensions/v1beta1   networking.k8s.io/v1   true      true       

This is happening on the linux amd64 version and the darwin arm64 version (installed via brew for the darwin install).

What did you expect to happen?

I expected pluto to output that the ingress component is using a removed api version

How can we reproduce this?

Create a repository for multiple helm charts (not packaged) and try running the pluto commands.
Explanation of how the detect-files command works would assist in troubleshooting.

Version

Latest

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

detect-files won't necessarily detect helm templates. You're better off using helm template | pluto detect.

We had a typo with the api version we were testing. Apologies.