The fixed values in the code that shape the operator's behaviour, and the defaults of the flags that tune
them. Each row names its source as file:line; line numbers can move between releases, so search for the
constant name when a line does not match. The design behind these values is in the
architecture.
drift interval of the access-critical kinds listed in scale and drift; flag --drift-interval-critical (cmd/main.go:104)
DefaultDriftIntervalStandard
1 h
internal/engine/drift.go:14
drift interval of every other kind; flag --drift-interval-standard (cmd/main.go:106)
MinDriftInterval
30 s
internal/engine/drift.go:42
CEL rejects a shorter spec.driftInterval (api/common/v1alpha1/types.go:120); the engine raises one that bypassed validation to 30 s
mountTableTTL
2 s
internal/controller/sys/mounttable.go:17
one read of sys/mounts or sys/auth serves every mount resource of the same connection and OpenBao namespace; a mount write or delete clears it, so an out-of-band mount change shows up to 2 s later
liveSnapshotTTL
10 s
internal/engine/ownership.go:157
one live LIST of a kind serves the ownership rechecks before adoption; a path this process claimed after that LIST gets a fresh LIST
jitter
× 0.8 to × 1.2
internal/engine/reconciler.go:1563-1564
applied to the drift requeue, to every backoff and to the pause recheck
minReferenceRetry
2 s
internal/engine/reconciler.go:55
first delay of every backoff below
backoff growth
time since Synced turned False with the same reason, at least 2 s
internal/engine/reconciler.go:1554-1561
each retry waits about as long as the condition has lasted, so the delay roughly doubles
retryInterval
30 s
internal/engine/reconciler.go:52
backoff cap for ReferenceNotReady and OutputNotDelivered
maxConnectionRetry
1 min
internal/engine/reconciler.go:54
backoff cap for ConnectionNotReady; the connection watch re-queues sooner
OutOfSync cap
the resource's drift interval
internal/engine/reconciler.go:886
backoff cap after a write that did not read back as written
inProgressInterval
10 s
internal/engine/reconciler.go:56
fixed requeue while OpenBao completes an asynchronous operation (ReconcileInProgress)
pausedRecheck
1 min
internal/engine/reconciler.go:59
recheck of a resource paused through its Namespace or its OpenBaoServer; a pause on the resource itself waits for the annotation change
requests without priority (drift reads, the first pass after an outage) use at most 80 % of OpenBaoServer.spec.rateLimit QPS and burst; spec changes may use all of it
rate limiter key
server address
internal/openbao/pool.go:72
one token bucket per address, shared by every connection to it; the most recent connection's rateLimit replaces the buckets
recoveryPerSecond
100 per second
internal/engine/budget.go:23
rate of the first passes after ConnectionNotReady, per OpenBaoServer
a renewal that returns a shorter lease (max TTL near) leads to a new login
replacement point, non-renewable token
two thirds of the TTL
internal/openbao/pool.go:443
a new login replaces the token
minReloginInterval
5 s
internal/openbao/pool.go:21
after a 401, or a 403 whose auth/token/lookup-self fails, at most one new login per 5 s per client; inside that window the request fails without a login
sharedLoginTimeout
1 min
internal/openbao/pool.go:28
limit of a login that several callers wait for
revokeTimeout
5 s
internal/openbao/pool.go:24
limit of the best-effort revocation of a retired token
tokenExpirationSeconds
600 s
internal/connection/resolver.go:57
lifetime requested for a TokenRequest token; each one is used for a single login
how long a client trusts the cluster id from sys/health; it is read again past the cache right before a create, a recreate and a delete
--cluster-id
the UID of the kube-system Namespace
cmd/main.go:117, :178-180, :260-266
written into ownership markers. A rebuilt Kubernetes cluster has a new kube-system UID, so markers written before the rebuild name another cluster and marked kinds (entities, groups, namespaces) report Conflict; a fixed --cluster-id survives the rebuild
workers of the kinds that usually have many objects (roles, policies, entities, groups)
--leader-elect
true
cmd/main.go:94
creates are serialised only within one process, so several replicas need it
GracefulShutdownTimeout
5 s
cmd/main.go:164-165
after SIGTERM in-flight reconciles get 5 s to return, within the chart's 10 s terminationGracePeriodSeconds; the leader then releases its lease (LeaderElectionReleaseOnCancel), so the next pod takes over without waiting for the lease to expire