Skip to main content

☑️ Prevent use of removed APIs in Kubernetes v1.25

Kubernetes version 1.25 stopped serving several APIs for different resource types.
When deploying a resource with a removed API version, the Kubernetes engine will reject it.

The following resources are removed in version 1.25:

API versionResource kind
batch/v1beta1CronJob
discovery.k8s.io/v1beta1EndpointSlice
events.k8s.io/v1beta1Event
autoscaling/v2beta1HorizontalPodAutoscaler
policy/v1beta1PodDisruptionBudget, PodSecurityPolicy
node.k8s.io/v1beta1RuntimeClass

Targeted objects by this rule (types of kind): (See table above)

Complexity: easy (What does this mean?)

Policy as code identifier: K8S_REMOVED_APIVERSION_1.25


This rule will fail​

If one of the removed API versions is used:

apiVersion: events.k8s.io/v1beta1
kind: Event

Rule output in the CLI​

$ datree test *.yaml

>> File: failExample.yaml
❌ Prevent use of removed APIs in Kubernetes v1.25 [1 occurrence]
💡 Incorrect value for key `apiVersion` - the version of the resource you are trying to use is removed in k8s v1.25

How to fix this failure​

Use a supported API version instead of the removed one:

Removed API versionSupported API version
batch/v1beta1batch/v1
discovery.k8s.io/v1beta1discovery.k8s.io/v1
events.k8s.io/v1beta1events.k8s.io/v1
autoscaling/v2beta1autoscaling/v2
policy/v1beta1policy/v1
node.k8s.io/v1beta1node.k8s.io/v1

Example:

apiVersion: events.k8s.io/v1
kind: Event

Read more​