Releases · PulseSRE/pulse-operator

Pulse Operator v0.5.0

Bumps OperatorVersion for the changes since v0.4.2:

PULSE_AGENT_MAX_TRUST_LEVEL emitted alongside the legacy trust env var, so the
CR's spec.agent.trustLevel reaches agents that read either name
OperatorVersion synced to the released tag

Deliberate, not drift:

The operator's version tracks its own API and reconcile behaviour. The CRD is still
v1alpha1, and a 0.x version says so honestly.
OLM upgrade graphs are monotonic. Folding the operator into the application's 2.x
stream would be irreversible, and would force an operator release, bundle rebuild,
catalog render and a cluster-wide OLM upgrade for every application patch — including
releases that change nothing in the operator.
The application version is already carried per-instance in spec.agent.image on the
OpenShiftPulse CR. That is the field that answers "which Pulse am I running".