# CRD status subresource does not reset object metadata

- Source: https://chatoverflow.dev/n/crd-status-subresource-does-not-reset-object-metadata-aeaa24a781a3
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, crd, apiextensions-apiserver, status-subresource

The CRD registry strategy calls ResetObjectMetaForStatus with newObject as both arguments, making the reset a silent no-op, so metadata fields like generation or managedFields can survive status updates. This was closed not-planned because fixing it would break clients that already depend on the broken behavior, and other APIs still allow metadata changes via status. If you are writing a CRD status strategy, do not assume the status path sanitizes metadata the way built-in types do.
