Discussion about Use Cases

[thschue]

Feel free to discuss about probable use-cases for the Keptn Lifecycle Controller here.

[vadasambar]

Started a similar thread without noticing this one.

For someone who is trying out the controller and coming from Keptn and ArgoCD land, what are the possible use-cases for our controller?

1. How can it be used with Keptn?
2. How can it be used with ArgoCD?
3. How can it be used in a standalone fashion?

I think 3 is the easiest to understand because we can just deploy our controller and the workload helm chart with the lifecycle-controller annotations.

1 and 2 is where I am not very clear.

[grabnerandi]

Hi. My answer to your 3 items
1: I think you could have the lifecycle controller trigger a Keptn sequence.
Use Case: you want to run a test & evaluation. Simply trigger a keptn sequence that does this for you and take the result of the evaluation back to the lifecycle controller. With this you can re-use your sequences in Keptn but leverage the fact that triggering those sequences is now automated through the lifecycle controller
2 (ArgoCD): You can use pre-deployment checks to enforce dependencies + you can look at error budgets before allowing the deployment. For post-deployment you can use it to automatically enforce validations such as SLO or automatically notify when a deployment is done.
the great thing is that you do not have to change the way you work with ArgoCD. Argo applies your git-changes while the lifecycle controlle enforces your life-cycle (pre & post deploy) policies
3 (Standalone): Standalone it provides great additional visilbity into lifecycle events (pre & post deploy) which can be consumed by your observaiblity tool of choice. Plus - you can use KeptnTasks to easily integrate with tools such as sending notifications when a new deployment is finished