From b835cbc6eb17fe7d279c1963c520130dda8d519a Mon Sep 17 00:00:00 2001 From: Jack Lucas Date: Tue, 5 Mar 2019 11:43:01 -0500 Subject: Undeploy k8s artifacts on timeout Issue-ID: DCAEGEN2-987 Change-Id: I35a2dcdb7b7f1b7280dba6593a9ee2b8921b6df9 Signed-off-by: Jack Lucas --- k8s/ChangeLog.md | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'k8s/ChangeLog.md') diff --git a/k8s/ChangeLog.md b/k8s/ChangeLog.md index 7c9a72c..3402581 100644 --- a/k8s/ChangeLog.md +++ b/k8s/ChangeLog.md @@ -5,6 +5,14 @@ All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](http://keepachangelog.com/) and this project adheres to [Semantic Versioning](http://semver.org/). +## [1.4.8] +* If an installation step times out because a component does not become ready within the maximum wait time, +delete the Kubernetes artifacts associated with the component. Previously, an installation step might time +out due to a very slow image pull. Cloudify would report a failure, but the component would come up, much +later, after Kubernetes finished pulling the image. This should no longer happen. + +## [1.4.7] +* Increase unit test coverage ## [1.4.6] * Support for specifying CPU and memory resources in a blueprint for a containerized component -- cgit 1.2.3-korg