Home / Docs / News / Release Announcements / Keptn 0.8.3
Keptn 0.8.3 implements the Keptn Enhancement Proposal #37 for allowing a Keptn user to customize the remediation sequence in the Shipyard. Besides, improvements for the user experience in the Bridge are implemented like setting the Git upstream repository or linking various screens.
Key announcements:
🎉 Customization of auto-remediation sequences: With this release, it is possible to customize the remediation sequences, which take care of resolving an open problem for a service. Therefore, the remediation sequence can be modeled in the Shipyard for a specific stage. Besides, it is possible to let the action-providers run on an execution plane.
- name: remediation
triggeredOn:
- event: [STAGE-NAME].remediation.finished
selector:
match:
evaluation.result: fail
tasks:
- name: get-action
- name: action
- name: evaluation
triggeredAfter: "10m"
properties:
timeframe: "10m"
⭐️ Length of service name increased to 43 characters: The limitation of the service name length has been loosened to allow a length of 43 characters.
🚀 Support custom deployment URLs: When deploying custom Helm Charts by using the user_managed
deployment strategy of the helm-service, it is now possible to define a public and/or local deployment URL. Therefore, the file endpoints.yaml
must be uploaded to the helm folder in the configuration repository. This file has to contain the deploymentURIsLocal
and/or deploymentURIsPublic
. For more details, please see the documentation here.
Many thanks to the community for the enhancements on this release!
Implemented Keptn spec version: 0.2.2
Platform Support / Installer
all: distributor: helm-service/jmeter-service: helm-service: jmeter-service: lighthouse-service: remediation-service: shipyard-controller:Keptn Core
Enhancements: Fixes:Bridge
- Response time degradation in configuration-service when using a Git Upstream (e.g., GitHub) 4066
- Response time degradation in lighthouse-service when spamming get-sli-events 4065
- Shipyard-controller keeps sending events for tasks with the same name indefinitely 4039
- Selection change in heatmap does not always update SLO table - needs second click 4007
- Mongodb OOM crash after flooding it with events 3968
- Open issues that will be fixed in upcoming releases
keptn upgrade
getLatestKeptnRelease returns the wrong version 3841
- Inconsistent usage of user-managed and user_managed causing issues 3624
The upgrade from 0.8.x to 0.8.3 is supported by the keptn upgrade
command. Find the documentation here: Upgrade from Keptn 0.8.x to 0.8.3