b0m123

I've run some more tests and I agree, `kubectl.kubernetes.io/restartedAt` annotation might not be relevant to that case, but still it's not working as expected. I'm not really sure what causes...

I was able to reproduce the error using Kubernetes API. PATCH request failed with 422 response code ``` curl --location --request PATCH 'https://testing.hostname.org:6443/apis/apps/v1/namespaces/default/deployments/ui' \ --header 'Content-Type: application/json-patch+json' \ --header 'Authorization:...

> > Btw, strategic-merge-patch works in both cases > > Can you test json merge (merge-patch+json) as well? It works in all cases ``` curl --location --request PATCH 'https://testing.hostname.org:6443/apis/apps/v1/namespaces/default/deployments/ui' \...

Just verified `json-patch+json` one more time. It's failing only if there is no annotation present in Pod template metadata. If I add any the request is working

Hi, I'm facing same problem... any updates here, please?