Being a DevOps Engineer / Site Reliability Engineer, you need to keep in your mind that Kubernetes changes its resources version with respect to time.
It was an issue that I found when the EKS version of my project was updated from 1.21 to 1.23, and because of parallel deployment, those changes had been updated by another team in the non-production environment, but those changes were not shared with the SRE team, resulting in a problem in the pre-production environment.
<ul>
<li>apiVersion changed in AWS EKS 1.23 version from 1.21 are -
 1) <code>apps/v1beta1</code> to <code>apps/v1</code> for Deployment
 2)<code>batch/v1</code> to <code>batch/v1beta1</code> for CronJob
 3)<a target="_blank" href="http://networking.k8s.io/v1beta1"><code>networking.k8s.io/v1beta1</code></a> to <a target="_blank" href="http://networking.k8s.io/v1"><code>networking.k8s.io/v1</code></a> for Ingress
</li>
</ul>

Being a DevOps Engineer / Site Reliability Engineer, you need to keep in your mind that Kubernetes changes its resources version with respect to time.

It was an issue that I found when the EKS version of my project was updated from 1.21 to 1.23, and because of parallel deployment, those changes had been updated by another team in the non-production environment, but those changes were not shared with the SRE team, resulting in a problem in the pre-production environment.

* apiVersion changed in AWS EKS 1.23 version from 1.21 are -
    
    1) `apps/v1beta1` to `apps/v1` for Deployment
    
    2)`batch/v1` to `batch/v1beta1` for CronJob
    
    3)[`networking.k8s.io/v1beta1`](http://networking.k8s.io/v1beta1) to [`networking.k8s.io/v1`](http://networking.k8s.io/v1) for Ingress

apiVerion Change - Kubernetes RealWorld Issues