What is Keptn Lifecycle Toolkit - with Giovanni Liva

[@holgerwinkelmann6219]

Is all this dependency mapping not a Cloud Native Anti Pattern? How will the scheduler know the Kafka will fail while in operations? Or what's the point of not deploying the workload if kafka or Postgres is not running or reachable in this deployment second but is available a moment later. The Apps should be robust enough to retry or might even go through a loop while waiting for the backing service to become available

[@isitobservable]

Hi, Yes it's a good point. but i like the ability to create pre-deployment checks to check that we have enough resources in the cluster for example. I think the value that klt brings is related to provide observability data from our deployments and generate an dashboard with our Dora metrics.
Recently KLT has added the metric server to extend the k8S metric server to expose metric from several observability provider. once the data is available in the k8s api we can imagine several valuable use case.

[@holgerwinkelmann6219]

@@isitobservable resource and environment checks are totally fine I think as well. Some infra baselines need to be checked Pre deployment, and some checks after deployment are also valuable, I’m just concerned about the complex dependency hell cloud native tried to avoid