What are the possible use-cases for our controller?

[vadasambar]

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.

[vadasambar]

Looks like there is another discussion thread here already: #39

[vadasambar]

Continuing the discussion here ^

[thschue]

Hello Suraj!

Thank you for your questions!

1. At the moment, there is no direct integration with Keptn. Although there is no focus on it at the moment, it might be that we will be able to trigger keptn events in the future.
2. You can use ArgoCD as you are used to, but the lifecycle controller can be used to provide pre- and post-deployment tasks and evaluations (quality gates in the Keptn v1 world) with a minimum change in your deployment manifests (everything is based on annotations, for applications you will need obviously a separate manifest). Furthermore, there will be application health checks which help you determining the App Readiness (!= pod health) in the future and with the last version we already added traces and metrics to the lifecycle controller, which helps you determining e.g, how often a workload has been deployed when it has been deployed and how long the whole process took.
3. The lifecycle-controller is designed to run stand-alone, so you don't need any control plane or external tools by default (except cert-manager and observability which can also be disabled). Therefore, Tasks are specified as Functions (there might be more to come), and evaluations will also triggered locally (nevertheless, the calculation will happen in the observability solution or an external service). You can simply apply your configuration via kubectl or your CD/GitOps Tool, and the Lifecycle Controller will do the rest :-)

[vadasambar]

Thank you for answering my questions 🙏