planetscale · jdoupe · Nov 23, 2025 · Dec 2, 2025 · Dec 5, 2025 · Apr 4, 2026
diff --git a/deploy/crds/planetscale.com_vitessbackupschedules.yaml b/deploy/crds/planetscale.com_vitessbackupschedules.yaml
@@ -44,6 +44,10 @@ spec:
                 - Forbid
                 example: Forbid
                 type: string
+              extraLabels:
+                additionalProperties:
+                  type: string
+                type: object
               failedJobsHistoryLimit:
                 format: int32
                 minimum: 0

diff --git a/deploy/crds/planetscale.com_vitessbackupstorages.yaml b/deploy/crds/planetscale.com_vitessbackupstorages.yaml
@@ -28,6 +28,10 @@ spec:
             type: object
           spec:
             properties:
+              extraLabels:
+                additionalProperties:
+                  type: string
+                type: object
               location:
                 properties:
                   annotations:

diff --git a/deploy/crds/planetscale.com_vitessclusters.yaml b/deploy/crds/planetscale.com_vitessclusters.yaml
@@ -36,6 +36,10 @@ spec:
                     - xtrabackup
                     - mysqlshell
                     type: string
+                  extraLabels:
+                    additionalProperties:
+                      type: string
+                    type: object
                   locations:
                     items:
                       properties:

diff --git a/docs/api.md b/docs/api.md
@@ -775,6 +775,20 @@ This is a list of VitessBackupScheduleTemplate where the &ldquo;name&rdquo; fiel
 across all the items of the list.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>extraLabels</code><br>
+<em>
+map[string]string
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>ExtraLabels can optionally be used to attach custom labels to pods created by backup schedules
+and the VitessBackupStorage subcontroller. These labels will be applied to both the backup
+schedule job pods and the subcontroller pod.</p>
+</td>
+</tr>
 </tbody>
 </table>
 <h3 id="planetscale.com/v2.ConcurrencyPolicy">ConcurrencyPolicy
@@ -2540,6 +2554,19 @@ Kubernetes core/v1.PullPolicy
 The PullPolicy used will be the same as the one used to pull the vtctld image.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>extraLabels</code><br>
+<em>
+map[string]string
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>ExtraLabels can optionally be used to attach custom labels to the pods created by VitessBackupSchedule.
+This is populated from ClusterBackupSpec.ExtraLabels when the schedule is created.</p>
+</td>
+</tr>
 </table>
 </td>
 </tr>
@@ -2628,6 +2655,19 @@ Kubernetes core/v1.PullPolicy
 The PullPolicy used will be the same as the one used to pull the vtctld image.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>extraLabels</code><br>
+<em>
+map[string]string
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>ExtraLabels can optionally be used to attach custom labels to the pods created by VitessBackupSchedule.
+This is populated from ClusterBackupSpec.ExtraLabels when the schedule is created.</p>
+</td>
+</tr>
 </tbody>
 </table>
 <h3 id="planetscale.com/v2.VitessBackupScheduleStatus">VitessBackupScheduleStatus
@@ -3232,6 +3272,19 @@ VitessBackupSubcontrollerSpec
 <p>Subcontroller specifies any parameters needed for launching the VitessBackupStorage subcontroller pod.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>extraLabels</code><br>
+<em>
+map[string]string
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>ExtraLabels can optionally be used to attach custom labels to the VitessBackupStorage subcontroller pod.
+This is populated from ClusterBackupSpec.ExtraLabels when the storage object is created.</p>
+</td>
+</tr>
 </table>
 </td>
 </tr>
@@ -3293,6 +3346,19 @@ VitessBackupSubcontrollerSpec
 <p>Subcontroller specifies any parameters needed for launching the VitessBackupStorage subcontroller pod.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>extraLabels</code><br>
+<em>
+map[string]string
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>ExtraLabels can optionally be used to attach custom labels to the VitessBackupStorage subcontroller pod.
+This is populated from ClusterBackupSpec.ExtraLabels when the storage object is created.</p>
+</td>
+</tr>
 </tbody>
 </table>
 <h3 id="planetscale.com/v2.VitessBackupStorageStatus">VitessBackupStorageStatus

diff --git a/docs/api/index.html b/docs/api/index.html
@@ -777,6 +777,20 @@ <h3 id="planetscale.com/v2.ClusterBackupSpec">ClusterBackupSpec
 across all the items of the list.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>extraLabels</code><br>
+<em>
+map[string]string
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>ExtraLabels can optionally be used to attach custom labels to pods created by backup schedules
+and the VitessBackupStorage subcontroller. These labels will be applied to both the backup
+schedule job pods and the subcontroller pod.</p>
+</td>
+</tr>
 </tbody>
 </table>
 <h3 id="planetscale.com/v2.ConcurrencyPolicy">ConcurrencyPolicy
@@ -2542,6 +2556,19 @@ <h3 id="planetscale.com/v2.VitessBackupSchedule">VitessBackupSchedule
 The PullPolicy used will be the same as the one used to pull the vtctld image.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>extraLabels</code><br>
+<em>
+map[string]string
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>ExtraLabels can optionally be used to attach custom labels to the pods created by VitessBackupSchedule.
+This is populated from ClusterBackupSpec.ExtraLabels when the schedule is created.</p>
+</td>
+</tr>
 </table>
 </td>
 </tr>
@@ -2630,6 +2657,19 @@ <h3 id="planetscale.com/v2.VitessBackupScheduleSpec">VitessBackupScheduleSpec
 The PullPolicy used will be the same as the one used to pull the vtctld image.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>extraLabels</code><br>
+<em>
+map[string]string
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>ExtraLabels can optionally be used to attach custom labels to the pods created by VitessBackupSchedule.
+This is populated from ClusterBackupSpec.ExtraLabels when the schedule is created.</p>
+</td>
+</tr>
 </tbody>
 </table>
 <h3 id="planetscale.com/v2.VitessBackupScheduleStatus">VitessBackupScheduleStatus
@@ -3234,6 +3274,19 @@ <h3 id="planetscale.com/v2.VitessBackupStorage">VitessBackupStorage
 <p>Subcontroller specifies any parameters needed for launching the VitessBackupStorage subcontroller pod.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>extraLabels</code><br>
+<em>
+map[string]string
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>ExtraLabels can optionally be used to attach custom labels to the VitessBackupStorage subcontroller pod.
+This is populated from ClusterBackupSpec.ExtraLabels when the storage object is created.</p>
+</td>
+</tr>
 </table>
 </td>
 </tr>
@@ -3295,6 +3348,19 @@ <h3 id="planetscale.com/v2.VitessBackupStorageSpec">VitessBackupStorageSpec
 <p>Subcontroller specifies any parameters needed for launching the VitessBackupStorage subcontroller pod.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>extraLabels</code><br>
+<em>
+map[string]string
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>ExtraLabels can optionally be used to attach custom labels to the VitessBackupStorage subcontroller pod.
+This is populated from ClusterBackupSpec.ExtraLabels when the storage object is created.</p>
+</td>
+</tr>
 </tbody>
 </table>
 <h3 id="planetscale.com/v2.VitessBackupStorageStatus">VitessBackupStorageStatus

diff --git a/pkg/apis/planetscale/v2/vitessbackupschedule_types.go b/pkg/apis/planetscale/v2/vitessbackupschedule_types.go
@@ -84,6 +84,11 @@ type VitessBackupScheduleSpec struct {
 	// ImagePullPolicy defines the policy to pull the Docker image in the job's pod.
 	// The PullPolicy used will be the same as the one used to pull the vtctld image.
 	ImagePullPolicy corev1.PullPolicy `json:"imagePullPolicy,omitempty"`
+
+	// ExtraLabels can optionally be used to attach custom labels to the pods created by VitessBackupSchedule.
+	// This is populated from ClusterBackupSpec.ExtraLabels when the schedule is created.
+	// +optional
+	ExtraLabels map[string]string `json:"extraLabels,omitempty"`
 }
 
 // VitessBackupScheduleTemplate contains all the user-specific fields that the user will be

diff --git a/pkg/apis/planetscale/v2/vitessbackupstorage_types.go b/pkg/apis/planetscale/v2/vitessbackupstorage_types.go
@@ -61,6 +61,10 @@ type VitessBackupStorageSpec struct {
 	Location VitessBackupLocation `json:"location"`
 	// Subcontroller specifies any parameters needed for launching the VitessBackupStorage subcontroller pod.
 	Subcontroller *VitessBackupSubcontrollerSpec `json:"subcontroller,omitempty"`
+	// ExtraLabels can optionally be used to attach custom labels to the VitessBackupStorage subcontroller pod.
+	// This is populated from ClusterBackupSpec.ExtraLabels when the storage object is created.
+	// +optional
+	ExtraLabels map[string]string `json:"extraLabels,omitempty"`
 }
 
 type VitessBackupSubcontrollerSpec struct {

diff --git a/pkg/apis/planetscale/v2/vitesscluster_types.go b/pkg/apis/planetscale/v2/vitesscluster_types.go
@@ -327,6 +327,12 @@ type ClusterBackupSpec struct {
 	// +patchMergeKey=name
 	// +patchStrategy=merge
 	Schedules []VitessBackupScheduleTemplate `json:"schedules,omitempty"`
+
+	// ExtraLabels can optionally be used to attach custom labels to pods created by backup schedules
+	// and the VitessBackupStorage subcontroller. These labels will be applied to both the backup
+	// schedule job pods and the subcontroller pod.
+	// +optional
+	ExtraLabels map[string]string `json:"extraLabels,omitempty"`
 }
 
 // VitessBackupEngine is the backup implementation to use.

diff --git a/pkg/apis/planetscale/v2/zz_generated.deepcopy.go b/pkg/apis/planetscale/v2/zz_generated.deepcopy.go
diff --git a/pkg/controller/vitessbackupschedule/vitessbackupschedule_controller.go b/pkg/controller/vitessbackupschedule/vitessbackupschedule_controller.go
@@ -43,6 +43,7 @@ import (
 	"planetscale.dev/vitess-operator/pkg/operator/reconciler"
 	"planetscale.dev/vitess-operator/pkg/operator/results"
 	"planetscale.dev/vitess-operator/pkg/operator/resync"
+	"planetscale.dev/vitess-operator/pkg/operator/update"
 	"planetscale.dev/vitess-operator/pkg/operator/vitessbackup"
 	"planetscale.dev/vitess-operator/pkg/operator/vttablet"
 	"sigs.k8s.io/controller-runtime/pkg/controller"
@@ -616,6 +617,10 @@ func (r *ReconcileVitessBackupsSchedule) createJob(
 		planetscalev2.KeyspaceLabel:       strategy.Keyspace,
 		planetscalev2.ShardLabel:          vkr.SafeName(),
 	}
+	// Merge user-provided extra labels.
+	if vbsc.Spec.ExtraLabels != nil {
+		update.Labels(&labels, vbsc.Spec.ExtraLabels)
+	}
 
 	meta := metav1.ObjectMeta{
 		Labels:      labels,
@@ -629,6 +634,10 @@ func (r *ReconcileVitessBackupsSchedule) createJob(
 	meta.Annotations[scheduledTimeAnnotation] = scheduledTime.Format(time.RFC3339)
 
 	maps.Copy(meta.Labels, vbsc.Labels)
+	// Merge user-provided extra labels into meta as well.
+	if vbsc.Spec.ExtraLabels != nil {
+		update.Labels(&meta.Labels, vbsc.Spec.ExtraLabels)
+	}
 
 	pod, vtbackupSpec, err := r.createJobPod(ctx, vbsc, strategy, name, vkr, labels)
 	if err != nil {

diff --git a/pkg/controller/vitessbackupstorage/reconcile_subcontroller.go b/pkg/controller/vitessbackupstorage/reconcile_subcontroller.go
@@ -69,6 +69,10 @@ func (r *ReconcileVitessBackupStorage) reconcileSubcontroller(ctx context.Contex
 		planetscalev2.ClusterLabel:   clusterName,
 		vitessbackup.LocationLabel:   vbs.Spec.Location.Name,
 	}
+	// Merge user-provided extra labels from ClusterBackupSpec.
+	if vbs.Spec.ExtraLabels != nil {
+		update.Labels(&labels, vbs.Spec.ExtraLabels)
+	}
 
 	spec, err := r.newSubcontrollerPodSpec(ctx, vbs)
 	if err != nil {