Kubernetes v1.35: Job Managed By Field Graduates to General Availability
Kubernetes version 1.35 has officially released the .spec.managedBy field for Jobs as a General Availability feature. This update allows external controllers to assume full responsibility for Job reconciliation, effectively bypassing the built-in Kubernetes Job controller for specific tasks. The primary objective is to facilitate advanced multi-cluster batch scheduling architectures, notably MultiKueue, which separates job dispatching in a Management Cluster from execution in Worker Clusters. This delegation mechanism enables users to track job status centrally without accessing remote clusters, addressing limitations in managed cloud environments where control planes are locked. The field operates in two modes: standard, where the built-in controller manages the job, and delegation, where an external controller takes over. To ensure stability, the field is immutable once set. Major ecosystem projects, including JobSet, Kubeflow Trainer, KubeRay, AppWrapper, and Tekton Pipelines, are adopting this interface to support cross-cluster orchestration. This development marks a significant step in standardizing control delegation within the Kubernetes batch ecosystem, offering granular management capabilities without requiring modifications to core controller manager flags.
Wire timeline
Kubernetes v1.35: Job Managed By Field Graduates to General Availability
Kubernetes version 1.35 has officially released the .spec.managedBy field for Jobs as a General Availability feature. This update allows external controllers to assume full responsibility for Job reconciliation, effectively bypassing the built-in Kubernetes Job controller for specific tasks. The primary objective is to facilitate advanced multi-cluster batch scheduling architectures, notably MultiKueue, which separates job dispatching in a Management Cluster from execution in Worker Clusters. This delegation mechanism enables users to track job status centrally without accessing remote clusters, addressing limitations in managed cloud environments where control planes are locked. The field operates in two modes: standard, where the built-in controller manages the job, and delegation, where an external controller takes over. To ensure stability, the field is immutable once set. Major ecosystem projects, including JobSet, Kubeflow Trainer, KubeRay, AppWrapper, and Tekton Pipelines, are adopting this interface to support cross-cluster orchestration. This development marks a significant step in standardizing control delegation within the Kubernetes batch ecosystem, offering granular management capabilities without requiring modifications to core controller manager flags.
Kubernetes Blog