Predrag Knezevic
Predrag Knezevic
> This is necesary because we no longer cache thelast-applied-configuration annotation, so when we add/remove the finalizers, we are removing that field from the metadata. This causes issues with clients...
> This is not a conflict issue. The problem was that we are using Update(), which uses the cached version of the resource to make the changes. The cached version...
@tmshort apologize I did not mention it earlier: moving to SSA requires also to migrate the information stored under `.metadata.managedField` - otherwise field removal would not be possible, see for...
> I will point out that managed fields is not a "bit of memory", but can double the size of the cache. The memory savings was significant. I agree, but...
> I agree the block could be clearer overall, but this PR doesnât change the behavior the comment describesâwe still only surface deprecation conditions when the catalog tells us something...