Kubernetes Scale Update Drops Spec.Replicas Manager Ownership
Is it fixed? Not yet.
Ongoing since Nov 16, 13:30 UTC. First reported Nov 16, 13:30 UTC.
What happened
A /scale update that keeps spec.replicas unchanged drops the creating manager's ownership of spec.replicas in Kubernetes deployments. This causes a later server-side apply to change the value without raising a conflict.
What caused it?
The first scale write incorrectly splits the kubectl-create entry of managedFields into two entries with the same manager, operation, and apiVersion, altering field ownership tracking.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on GitHub issue
A `/scale` update that keeps `spec.replicas` unchanged drops the creating manager's ownership of `spec.replicas`; a later server-side apply then changes it without a conflict
Source
Evidence
1 report · 1 GitHubShow
- [1]GitHub First reportA `/scale` update that keeps `spec.replicas` unchanged drops the creating manager's ownership of `spec.replicas`; a later server-side apply then changes it without a conflict(opens GitHub issue in a new tab)
What happened? A Deployment is created with kubectl create (manager kubectl-create, operation Update) and spec.replicas: 2. A server-side apply of spec.replicas: 5 by another manager is refused with a conflict, as documented. Then kubectl scale --replicas=2 is run twice, which does not change the value. The first scale write splits the kubectl-create entry of managedFields into two entries with the same manager, operation and apiVersion: one without time that owns only spec.replicas, and one…
by jiren-the-gray 0upvotes 3comments
FAQ
What happened in the Kubernetes issue?
A /scale update that keeps spec.replicas unchanged drops the creating manager's ownership of spec.replicas in Kubernetes deployments. This causes a later server-side apply to change the value without raising a conflict.
What is affected by the Kubernetes issue?
Kubernetes.
When did the Kubernetes issue start and end?
It started Nov 16, 13:30 UTC and is still ongoing (2 d 15 h so far). This page updates as it develops.
How do I get alerts for Kubernetes?
Subscribe to the Kubernetes RSS feed for every new Kubernetes incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Kubernetes is down. Kubernetes feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.