From 3f9ab7fb93c91160670623bbe04897005b6bbc4d Mon Sep 17 00:00:00 2001 From: Richa Banker Date: Mon, 25 Mar 2024 11:36:05 -0700 Subject: [PATCH] Update keps/sig-api-machinery/2339-storageversion-api-for-ha-api-servers/README.md Co-authored-by: Joe Betz --- .../2339-storageversion-api-for-ha-api-servers/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/keps/sig-api-machinery/2339-storageversion-api-for-ha-api-servers/README.md b/keps/sig-api-machinery/2339-storageversion-api-for-ha-api-servers/README.md index adf5add6f6b..abdabf3aa93 100644 --- a/keps/sig-api-machinery/2339-storageversion-api-for-ha-api-servers/README.md +++ b/keps/sig-api-machinery/2339-storageversion-api-for-ha-api-servers/README.md @@ -353,7 +353,7 @@ correct order. 1. Storageversion updates will be triggered by CRD create and update watch events 2. We will perform async updates of storageversions such that we do not block writes of other unrelated APIs(for ex, crdA writes waiting for update of crdB's storageversion). These requests should be handled asynchronously -3. We will block a storageversion update until the teardown of prev storage is finished +3. We will block a storageversion update until the teardown of prev CRD storage is finished. If reconciliation finds storageversions requiring update and it detects that the CRD storage has already been updated, the storageversion can be updated immediately 1. this means we will wait to update storageversion of a CRD until 1. old storage of the same CRD is deleted 2. pending CR writes using old storageversion of the same CRD are completed