A CEL compile error in one health rule stops the health assessment of the Release
A failing mutation stops a pinned rollback and the rollout state machine
A forced sync is used up by a reconcile that fails before the apply
A pruned object can come back in the ReleaseInventory as a health-only entry
A reconcile that stops before the sync clears status.waves
A render that fails the dry run keeps the rollout in Progressing
A replica that cannot list members keeps its shards after its leases expire
A transient read error can restart the health deadline of a resource
A wave failure does not record the wave number in status.lastAttempted.failure
A wave gate can pass on health from the previous render
A wave timeout can count from the apply time of an earlier render
Deleting a Release deletes its CRDs and Namespaces, also when the prune policy protects them
In manual sync mode, writes other than /sync can start an apply
Manual sync mode can apply without a /sync request
OCIRegistry rejects an empty defaultContentType
Proxied subresources can return 404 with more than one observer replica
releaseNamespace and targetNamespace do not set the namespace of rendered objects
The API docs say that waveStrategy.timeout waits without a limit, but a syncWave mutation gets 30s
Without a render store, status reports a rollback that did not occur
Without health assessment, lastHealthy can point to a render that was never applied

Get started

Install convoy and deploy a first Release.

Describes convoy v0.9.0.