Keptn 0.7.1 improves the capabilities of the 0.7.0 release by adding more flexibility to the tasks of installing/operating Keptn, introducing three new CLI commands and improving the UX in the Keptn Bridge. Especially the new feature of installing Keptn in different namespaces is a door opener for various use-cases since multiple Keptn deployments, e.g., one for each team, can be operated on one cluster.
The key announcements of Keptn 0.7.1:
🌟 More flexibility in installing/operating Keptn:
keptn install --namespace: Allows you to specify the namespace to install Keptn in.
keptn upgrade: Instead of manually executing a K8s job as done by the previous upgrade processes, this CLI command performs the upgrade.
root context: As part of the installation Helm Chart of Keptn, a root context can be specified that allows you to customize the prefix of the API and Bridge endpoint of Keptn.
🚀 New CLI commands:
keptn delete service: This command will delete a service from a project and undeploy the service from the cluster.
keptn get events: This command is a generic implementation to retrieve Keptn events of any event type.
✨ UX improvements in environment screen: Based on feedback on the features of the Keptn delivery assistant, improvements regarding the user experience of the Keptn Bridge has been implemented.
🎉 Keptn on OpenShift 4: Thanks to the work of @marcredhat, Keptn has been successfully tested on an OpenShift 4 cluster. Two assets of this task are provided here: (1) Docu for Automated install of OpenShift 4.5 and Keptn and (2) YouTube - Deploy to OpenShift 4.5 / Service Mesh using Keptn.
Implemented Keptn spec version: 0.1.5
Platform Support / Installer
keptn install --namespace= #2195
keptn upgrade #2234
/event endpoint when no event is found #1655
keptn delete to delete a service from a Keptn project #2199
keptn get event command #2207
keptn get event to get an event of any event type #2171
keptn add-resource checks the number of arguments before executing the command #1735
keptn auth command in user menu #2197
problem.resolved event #2139