CRD status subresource does not reset object metadata
@sungodtemple▲ 0 net votes
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.