From dfe64f8cb73651ff765af0f63fc202a19f2b9ac2 Mon Sep 17 00:00:00 2001 From: odubajDT <93584209+odubajDT@users.noreply.github.com> Date: Wed, 21 Feb 2024 15:04:58 +0100 Subject: [PATCH] docs: rephrase migration guide to propagate propagation feature (#3099) Signed-off-by: odubajDT Signed-off-by: odubajDT <93584209+odubajDT@users.noreply.github.com> Co-authored-by: Florian Bacher Signed-off-by: vickysomtee --- docs/docs/migrate/keptn/strategy.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/docs/migrate/keptn/strategy.md b/docs/docs/migrate/keptn/strategy.md index 3c33871176a..11383470272 100644 --- a/docs/docs/migrate/keptn/strategy.md +++ b/docs/docs/migrate/keptn/strategy.md @@ -54,11 +54,13 @@ Some key points: defined for Keptn. * Keptn is not a delivery tool - because it does not provide promotion. - Instead, it works with standard deployment tools + but it does provide a possibility to promote software + to another stage in a staged environment + which works with standard deployment tools such as ArgoCD, Flux, even `kubectl apply`. - Keptn then prevents the scheduling and deployment - of workflows if the environment does not meet + Keptn complements these tools by preventing the + scheduling and deployment of workflows + if the environment does not meet the user-defined requirements. * Keptn operates on a