Datadog Cluster Agent warning about CronJob deprecation

[adammw]

batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob

Tested with cluster-agent 1.16.0 and Kubernetes v1.21.6.

[mscanlon72]

As well as this:

policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget

[SpikePy]

Please fix this, its spamming our log (80k entries per day) and as you might already know ... we have to pay for each log entry. its not nice to let your customers pay for problems you cause with your own software!

[sashasimkin]

I'm having the same issue, and I'd gladly look for a way to use new API versions, but the problem is - I don't have deprecated resources in the cluster 🤔

$ k get poddisruptionbudgets.policy --all-namespaces -o json | jq '.items[].apiVersion'
"policy/v1"
$ k get cronjob --all-namespaces -o json | jq '.items[].apiVersion'
$ # No cronjobs in the cluster

[epk]

Fixed in https://github.com/DataDog/datadog-agent/pull/11126

[NemanjaMilenkovic]

Hi! Although warnings should be silenced by https://github.com/DataDog/datadog-agent/pull/11126, there are still calls/logs to removed API made:

As this issue is still opened - are there any updates on this?

(GKE) Kubernetes Version: "1.26.10-gke.1101000" Helm Release Version: "3.1.9" Datadog Cluster Agent/Agent Version: "7.39.0"