Kubernetes API Deprecations

Question

Kubernetes API Deprecations

Rodolfo M 5

Hi all,

I had a warning in the "Diagnose and solve problems" issue in the Azure portal because my cluster was out of date, and I was a deployment with the autoscaling/v2beta2 api.

Last week, I updated my cluster to 1.25.6 Kubernetes version + agents and migrated my deployment to autoscaling/v2.

Both (AKS and HPA) are working fine without issues, but yesterday I got the same warning saying "Detected the use of APIs that have a deprecation warning for a previous, current, or future Kubernetes version" in "Diagnose and solve problems."

Does anyone face the same issue?

Thanks!

Prrudram-MSFT 28,201 Reputation points Moderator

2023-06-23T19:05:59.78+00:00

Hello @Rodolfo M

If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!
Prrudram-MSFT 28,201 Reputation points Moderator

2023-07-04T18:18:18.06+00:00

@Rodolfo M

If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

4 answers

Your answer

Prrudram-MSFT 28,201 Reputation points Moderator

2023-06-23T19:05:59.78+00:00

Hello @Rodolfo M

If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!
Prrudram-MSFT 28,201 Reputation points Moderator

2023-07-04T18:18:18.06+00:00

@Rodolfo M

If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

Answer 1

Mutaz Nassar 2,361 Microsoft Employee

Hi @Rodolfo M

Make sure to select the time rage for the last 1 hour to verify if you still see the warning.

Also you can verify directly on your AKS cluster using this command:
kubectl get --raw /metrics | grep apiserver_requested_deprecated_apis

Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.

Rodolfo M 5 Reputation points

2023-06-19T16:08:13.9333333+00:00

Hi @Mutaz Nassar

Thanks for the help. Yes, I have changed the rage time and I'm still seeing the warning. I'm pasting both screenshots (warning and command).
Rodolfo M 5 Reputation points

2023-06-19T16:08:41.91+00:00
Rodolfo M 5 Reputation points

2023-06-19T16:10:16.42+00:00

This is the result of the command.
Mutaz Nassar 2,361 Reputation points Microsoft Employee

2023-06-19T16:35:01.2466667+00:00

This is a watch verb which means that there is another object in your cluster like Keda, Datadog, or Splunk, is sending an HTTP GET request with the ?watch query parameter with this API version which means that this warning is not related to the HPA deployment itself, you can check your applications to verify if there is any watch call for this API version.

Hope this helps, and please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.

Answer 2

https://stackoverflow.com/questions/76391104/detected-the-use-of-apis-that-have-a-deprecation-warning-for-a-previous-current

https://kubernetes.io/docs/reference/using-api/deprecation-guide/

https://learn.microsoft.com/en-us/answers/questions/1311962/kubernetes-api-deprecations

in addition to mutaz comment as per above refs

With the 1.25.6 update, the API versions batch/v1beta1 for CronJob and discovery.k8s.io/v1beta1 for EndpointSlice are no longer served, and the objects using these APIs should be migrated to their new versions: batch/v1 and discovery.k8s.io/v1 respectively

Answer 3

Hello Rodolfo,

Best link to check deprecated API's is the following:

https://kubernetes.io/docs/reference/using-api/deprecation-guide/#horizontalpodautoscaler-v126

I pointed the specific API that you mentioned but therae are others that you need to manually check, if you are using any depcreated APIs then it is expected that you see the warning.

In addition, we recently released a feature that prevents a cluster upgrade if the target cluster introduces API breaking changes:

https://learn.microsoft.com/en-us/azure/aks/upgrade-cluster?tabs=azure-cli#stop-cluster-upgrades-automatically-on-api-breaking-changes-preview

Thanks!

Answer 4

Rodolfo M 5

Hi @Everybody

The problem was "metrics-server" deployment was using the deprecated API.

Thanks all for the help.

Regards!

Share via

Kubernetes API Deprecations

4 answers

Your answer