Skip to content

Commit a51a89a

Browse files
committed
wip
Signed-off-by: Attila Mészáros <[email protected]>
1 parent 7519920 commit a51a89a

File tree

1 file changed

+21
-1
lines changed

1 file changed

+21
-1
lines changed

docs/content/en/blog/news/nonssa-vs-ssa.md

+21-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: From client side to server side apply
2+
title: From client side to server-side apply
33
date: 2025-02-17
44
---
55

@@ -18,6 +18,26 @@ For dependent resources a separate flag exists (this was true also before v5) to
1818

1919
## Resource handling without and with SSA
2020

21+
Until version 5 changing primary resource through `UpdateControl` did not use server-side apply.
22+
So usually the implementation of reconciler looked something like this:
23+
24+
```java
25+
26+
@Override
27+
public UpdateControl<WebPage> reconcile(WebPage webPage, Context<WebPage> context) {
28+
29+
reconcileLogicForManagedResources(webPage);
30+
webPage.setStatus(updatedStatusForWebPage(webPage));
31+
32+
return UpdateControl.patchStatus(webPage);
33+
}
34+
35+
```
36+
37+
In other words, after reconciliation of managed resources the reconcile updated the status on the
38+
primary resource passed as argument to the reconciler.
39+
Such changes on primary are fine, since we don't work directly with the cached object, the argument is
40+
already cloned.
2141

2242
## Migrating to SSA
2343

0 commit comments

Comments
 (0)