What version of Knative?
1.22.0
Expected Behavior
A deployment is scaled up or down by autoscaler.
Actual Behavior
There are internal errors such as:
{
"insertId": "ep4uyzcmfxz4tqfa",
"jsonPayload": {
"logger": "autoscaler.event-broadcaster",
"commit": "370ad5a",
"timestamp": "2026-05-21T07:35:33.930551477Z",
"caller": "record/event.go:377",
"message": "Event(v1.ObjectReference{Kind:\"PodAutoscaler\", Namespace:\"headless-customer\", Name:\"hqbht9iojq2hf8njzu18pcsnz-00008\", UID:\"a431f570-bfd3-4349-b699-c27ce693c175\", APIVersion:\"autoscaling.internal.knative.dev/v1alpha1\", ResourceVersion:\"1779341502140639018\", FieldPath:\"\"}): type: 'Warning' reason: 'InternalError' error scaling target: failed to apply scale 0 to scale target hqbht9iojq2hf8njzu18pcsnz-00008-deployment: Internal error occurred: add operation does not apply: doc is missing path: \"/spec/template/metadata/labels\": missing value"
},
"resource": {
"type": "k8s_container",
"labels": {
"container_name": "autoscaler",
"project_id": "wp-engine-headless-dev",
"namespace_name": "knative-serving",
"cluster_name": "dev-us-central1-data-1",
"location": "us-central1",
"pod_name": "autoscaler-6ff64864bc-6crfm"
}
},
"timestamp": "2026-05-21T07:35:33.930664297Z",
"severity": "INFO",
"labels": {
"k8s-pod/repo": "headless-infra",
"k8s-pod/pod-template-hash": "6ff64864bc",
"k8s-pod/app": "autoscaler",
"k8s-pod/app_kubernetes_io/name": "knative-serving",
"k8s-pod/jira": "NEB",
"k8s-pod/app_kubernetes_io/component": "autoscaler",
"k8s-pod/slack": "atlas-infrastructure-monitoring",
"compute.googleapis.com/resource_name": "gke-dev-us-central1--dev-us-central1--7fcf9d9a-t2yh",
"k8s-pod/app_kubernetes_io/version": "1.22.0",
"k8s-pod/owner": "pe-atlas-nebula",
"k8s-pod/topology_kubernetes_io/region": "us-central1",
"k8s-pod/topology_kubernetes_io/zone": "us-central1-c",
"k8s-pod/team": "nebula"
},
"logName": "projects/wp-engine-headless-dev/logs/stderr",
"receiveTimestamp": "2026-05-21T07:35:38.628480138Z"
}
Another example:
{
"insertId": "4ev65mtc3qqcki46",
"jsonPayload": {
"commit": "370ad5a",
"timestamp": "2026-05-21T07:19:07.692521554Z",
"caller": "record/event.go:377",
"message": "Event(v1.ObjectReference{Kind:\"PodAutoscaler\", Namespace:\"headless-customer\", Name:\"h8qhg50z882e25jm6l90hyqom-00006\", UID:\"c6b08ad2-f0c2-47ab-a6b9-54147320ae2d\", APIVersion:\"autoscaling.internal.knative.dev/v1alpha1\", ResourceVersion:\"1779175295378063018\", FieldPath:\"\"}): type: 'Warning' reason: 'InternalError' error scaling target: failed to apply scale 1 to scale target h8qhg50z882e25jm6l90hyqom-00006-deployment: Internal error occurred: add operation does not apply: doc is missing path: \"/spec/template/metadata/labels\": missing value",
"logger": "autoscaler.event-broadcaster"
},
"resource": {
"type": "k8s_container",
"labels": {
"pod_name": "autoscaler-6ff64864bc-6crfm",
"project_id": "wp-engine-headless-dev",
"namespace_name": "knative-serving",
"cluster_name": "dev-us-central1-data-1",
"location": "us-central1",
"container_name": "autoscaler"
}
},
"timestamp": "2026-05-21T07:19:07.692780384Z",
"severity": "INFO",
"labels": {
"k8s-pod/pod-template-hash": "6ff64864bc",
"k8s-pod/owner": "pe-atlas-nebula",
"k8s-pod/app_kubernetes_io/version": "1.22.0",
"k8s-pod/slack": "atlas-infrastructure-monitoring",
"k8s-pod/team": "nebula",
"k8s-pod/app_kubernetes_io/name": "knative-serving",
"k8s-pod/app": "autoscaler",
"k8s-pod/jira": "NEB",
"k8s-pod/repo": "headless-infra",
"k8s-pod/topology_kubernetes_io/region": "us-central1",
"k8s-pod/topology_kubernetes_io/zone": "us-central1-c",
"compute.googleapis.com/resource_name": "gke-dev-us-central1--dev-us-central1--7fcf9d9a-t2yh",
"k8s-pod/app_kubernetes_io/component": "autoscaler"
},
"logName": "projects/wp-engine-headless-dev/logs/stderr",
"receiveTimestamp": "2026-05-21T07:19:08.706395958Z"
}
Steps to Reproduce the Problem
The problems started to happen after upgrading knative to 1.22.0
What version of Knative?
1.22.0
Expected Behavior
A deployment is scaled up or down by autoscaler.
Actual Behavior
There are internal errors such as:
Another example:
Steps to Reproduce the Problem
The problems started to happen after upgrading knative to 1.22.0