Important Changes
Introduces deeper support for release automation with a wider range of HTTP traffic metrics and the integration of release plans into the Release Agents.
Additional request count and response timemetrics have been added. These are grouped by HTTP request type to allow policy conditions to be set for GET, POST, PUT and DELETE etc requests.
This provides improved support for the SRE concept of Service Level Objectives (SLOs), specifically the monitoring of latency-based SLOs.
The release plans have been moved into Vault and release plan based triggers have been added to the Release Agents.
In previous versions, release plans were external artifacts stored in git repos and using them required adding additional scripts to your CD pipeline.
Changed the default Pulse event type from
elasticsearchtonatsChanged Lifter to deploy NATS Streaming Server as a dependency
Added request count and response time
metricsgrouped by HTTP request typeAdded a NATS streaming channel for release plan events
Fixed
/eventsAPI endpoint returns 503 error when Elasticsearch index doesn't existFixed
allocationmetrics showminAvailable: truewhen a Deployment has no Pods (Kubernetes)Fixed Lifter does not create Service Account for the Quantification workflow (Kubernetes)
The internal, shared event queue has been replaced with individual, external event queues based on the NATS Streaming.
The internal event queue did not support durable subscriptions and the event delivery to the Workflows could fail, most noticeably immediately after a restart.
Changed Kubernetes
livenessProbeto include all API endpointsChanged the
healthmetric on Kubernetes to include a delta of the Pod restart countAdded NATS Streaming Server as a required component
Added NATS Streaming as a Pulse event type
Fixed multiple Pulse events are triggered when editing a Gateway in UI
Fixed VGA templates cannot be updated through the Lifter UI
Optimised the MySQL connection management to improve startup time.
