use policy/v1 for PodDisruptionBudget

[a7i]

What does this PR change?

• uses policy/v1 for listing PDBs

Does this PR relate to any other PRs?

• No

How will this PR impact users?

• policy/v1beta1 is no longer served as of 1.25

Does this PR address any GitHub or Zendesk issues?

• Closes ...

How was this PR tested?

Does this PR require changes to documentation?

Have you labeled this PR and its corresponding Issue as "next release" if it should be part of the next OpenCost release? If not, why not?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
opencost	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 5, 2024 6:13pm

[mattray]

@a7i thanks for opening this! Looking at the Kubernetes API documentation I see this API was removed in 1.25 and available since 1.21. This means we should update
https://www.opencost.io/docs/installation/install
and Kubecost should update
https://docs.kubecost.com/install-and-configure/install/environment#supported-kubernetes-versions
accordingly.

[mattray]

I want another @opencost/opencost-maintainers to merge it, but it looks good to me.

[michaelmdresser]

If I'm reading K8s notes correctly, policy/v1 PodDisruptionBudget was added in K8s v1.21 (https://github.com/kubernetes/sig-release/blob/master/releases/release-1.21/release-notes/release-notes-draft.md). I think that's enough prior versions of support for us to roll forward with only supporting policy/v1 PDBs.

EDIT: Matt, I can't read. Thank you for doing the research.

[michaelmdresser]

Hey @AjayTripathy -- heads up that this will bump KC's min K8s version from v1.20 to v1.21, but I think it might only affect Spot Commander.

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud