@dmgnr/kuber 2.3.4 → 2.4.1

package/README.md

@@ -83,8 +83,8 @@ days; `logout` revokes the server-side session. `readSession` falls back to the
 persistent file when no runtime session exists.
 
 The default login is scoped to the current user and the authenticated identity
-is available to every v2 command. `login`, `logout`, and `whoami` are the only
-commands that run without a loaded project configuration.
+is available to every v2 command. `login`, `logout`, `whoami`, and global
+`maintenance` are the only commands that run without a loaded project configuration.
 
 ### Roles and Authorization
 
@@ -253,6 +253,19 @@ variables:
   registry access.
 - `KUBER_BUILDKIT_IMAGE`: override the BuildKit runner image used for builds.
 - `KUBER_BUILD_DATA_CLAIM`: the PVC claim backing builds.
+- `KUBER_BUILD_RECONCILE_MS` (default `30000`): the background build
+  reconciliation interval in milliseconds. Values must be greater than zero and
+  no greater than `2147483647` (the JavaScript timer maximum); invalid values
+  use the default.
+- `KUBER_BUILD_RECONCILE_TIMEOUT_MS` (default `20000`, maximum `25000`): the
+  deadline for one background build-reconciliation scan in milliseconds. The
+  maximum leaves time within the 30-second reconciliation lease for normal
+  renewal or release. The reconciler renews both its workspace and per-build
+  leases every 10 seconds for the lifetime of a generation, including while an
+  observation, log read, or store call is pending. On timeout its abort signal
+  is cancelled and logged, but Kubernetes requests may be unabortable; the
+  generation remains active and continues its lease heartbeat until that request
+  settles, so a later scan cannot overlap it.
 
 See [Server Deployment](#server-deployment) for how `compose.yml` wires the
 internal registry variables for the kuber-server pod.