Closed lg-d closed 8 months ago
Hi, I've been preparing an EKS upgrade from 1.25 to 1.26, upon using Pluto it's detecting versions of APIs which aren't being used.
Command: pluto detect-helm -o yaml --target-versions k8s=v1.26.0
Snipped command output:
- name: redacted/redacted namespace: production api: version: autoscaling/v2beta2 kind: HorizontalPodAutoscaler deprecated-in: v1.23.0 removed-in: v1.26.0 replacement-api: autoscaling/v2 replacement-available-in: "" component: k8s deprecated: true removed: true replacementAvailable: true
Whereas the actual HPA is running the correct API:
apiVersion: autoscaling/v2 kind: HorizontalPodAutoscaler metadata: annotations:
Am I misunderstanding what Pluto is telling me? is this normal behaviour?
Not to see the API listed if it's running the correct version
Run the command I gave above, it may or may not give you the same result.
Version:5.18.2 Commit:ad7a2381ecb2ba4cca6fdf2e8dddd18660327035
No response
What happened?
Hi, I've been preparing an EKS upgrade from 1.25 to 1.26, upon using Pluto it's detecting versions of APIs which aren't being used.
Command: pluto detect-helm -o yaml --target-versions k8s=v1.26.0
Snipped command output:
Whereas the actual HPA is running the correct API:
Am I misunderstanding what Pluto is telling me? is this normal behaviour?
What did you expect to happen?
Not to see the API listed if it's running the correct version
How can we reproduce this?
Run the command I gave above, it may or may not give you the same result.
Version
Version:5.18.2 Commit:ad7a2381ecb2ba4cca6fdf2e8dddd18660327035
Search
Code of Conduct
Additional context
No response