wip

Signed-off-by: Attila Mészáros <[email protected]>

Author: csviri

docs/content/en/blog/news/primary-cache-for-next-recon.md

@@ -29,8 +29,7 @@ if you use it, the framework guarantees that the next reconciliation will always
 
     // omitted code
 
-    var freshCopy = createFreshCopy(resource);
-
+    var freshCopy = createFreshCopy(resource); // need fresh copy just because we use the SSA version of update
     freshCopy
         .getStatus()
         .setValue(statusWithAllocatedValue());
@@ -63,5 +62,5 @@ If we do an update with optimistic locking it simplifies the situation, we can e
 Since we know if the update with optimistic locking is successful, we had the fresh resource in our cache. 
 Thus, the next event we receive will be the one that is results of our update or a newer one. 
 So if we cache the resource in the overlay cache we know that with the next event, we can remove it from there.
-
-
+If the update with optimistic locking fails, we can wait until the informer's cache is populated with next resource
+version and retry.