New Features in Kubernetes 1.30 Summary

Kubernetes 1.30 Overview

Kubernetes 1.30 “Uwubernetes” was released in April 2024. It includes 45 feature enhancements, with 17 graduating to Stable.

Major New Features

1. Pod Scheduling Readiness (GA)

The feature to control whether a Pod is schedulable has reached GA.

apiVersion: v1
kind: Pod
metadata:
  name: my-pod
spec:
  schedulingGates:
  - name: example.com/wait-for-resources
  containers:
  - name: app
    image: nginx

2. PodDisruptionConditions (GA)

You can now understand in detail why a Pod was disrupted.

# Check Pod status
kubectl get pod my-pod -o jsonpath='{.status.conditions}'

3. Min Domains in PodTopologySpread (GA)

You can now specify minimum domain count in PodTopologySpreadConstraints.

topologySpreadConstraints:
- maxSkew: 1
  topologyKey: topology.kubernetes.io/zone
  minDomains: 3
  whenUnsatisfiable: DoNotSchedule

What is GA: Abbreviation for General Availability, meaning a stable feature recommended for production use.

Features Graduated to Beta

Recursive Read-only Mounts

Submounts within mounted volumes can be recursively made read-only.

volumeMounts:
- name: data
  mountPath: /data
  readOnly: true
  recursiveReadOnly: Enabled

Job Success/Failure Policy

More fine-grained control over Job success/failure conditions.

Deprecated/Removed Features

Removed

• SecurityContextDeny admission plugin
• Old cloud provider related features

Deprecated

• status.nodeInfo.kubeProxyVersion field
• Some old API versions

Upgrade Considerations

• Confirm you’re not using removed features
• Plan migration if using deprecated APIs
• Back up cluster before upgrading
• Pre-test in staging environment

# Check current version
kubectl version

# Check deprecated API usage
kubectl get --raw /metrics | grep apiserver_requested_deprecated_apis

Summary

Kubernetes 1.30 has many scheduling and Pod management features graduating to GA, making production use more reliable. Don’t forget to check deprecated features when upgrading.