Closed StackScribe closed 11 months ago
KLT by design does not support this functionality.
Is this supposed to read KLT by design does not support this functionality (yet)
or is the intention that KLT will (and that's what you wish to document)?
As I understand it, by design, KLT does not and will not implement this functionality itself because KLT is not a pipeline. It is expected that this functionality will be handled by ArgoCD or Flux -- not sure about kubectl --apply . And, of course, we don't want to start documenting ArgoCD, etc functionality, but we may need to say a little bit more about how one implements this in the major deployment engines.
I think that feature is very dependeny on whatever other deployment tools users are using. So I think by documenting this, we implicitely are documenting that tool instead of ours. So I don't think we really need to implement/document anything here. I will close this for now. If there are any objections, please re-open :)
Part of https://github.com/keptn/lifecycle-toolkit/issues/1499
Keptn v1 enables the user to run an evaluation, then run tasks based on the results of that evaluation, and then do another evaluation. KLT by design does not support this functionality. Instead, it can be implemented using Argo Workflows, Tekton, and other tools.
We need a page that explains how to do this and provides an example of this segment of Keptn v1 functionality and how to implement it using other tools.