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
Code of Conduct
Additional context
No response
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.22This 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
Code of Conduct
Additional context
No response