liveBook · Manning

Keptn Lifecycle Operator

As explained in Platform Engineering on Kubernetes

The Keptn Lifecycle Toolkit is a cloud-native toolkit for observing deployments, accessing deployment data, and orchestrating deployment checks and actions.

Keptn Lifecycle Toolkit is a cloud-native lifecycle orchestration toolkit for deployment observability, deployment-data access, and deployment-check orchestration. It also provides mechanisms to check workloads and act when problems occur. section 9.3

Keptn extends the Kubernetes Scheduler to monitor workloads and extract deployment information. Teams define custom pre- and post-deployment tasks with Keptn TaskDefinition resources. section 9.3

Configure lifecycle monitoring through standard Kubernetes metadata and task hooks:

  • Annotate services with application name, logical grouping, and version metadata. section 9.3
  • Enable the lifecycle toolkit on a namespace with kubectl annotate ns default keptn.sh/lifecycle-toolkit="enabled". section 9.3
  • Attach a post-deployment task through keptn.sh/post-deployment-tasks and execute inline Deno code with deployment context. section 9.3

Conference application lifecycle hook

The Agenda service uses Kubernetes annotations to identify the service and its application grouping. A notifications service can attach a stdout task that receives workload name, application name, workload version, task type, and object type after deployment. section 9.3

Figure 9.21 Keptn architecture providing out-of-the-box observability and application lifecycle hooks.

Use the architecture diagram to trace how observability and application lifecycle hooks extend Kubernetes deployment workflows. section 9.3

How Platform Engineering on Kubernetes covers it

How deep it goes
Explains scheduler integration, annotations, namespace activation, and task definitions, while linking to a fuller step-by-step tutorial.
Examples
Uses the Conference Agenda and notifications services, Kubernetes annotations, a Deno task, and expected task context output.
What it assumes
Assumes Kubernetes workload and namespace familiarity, while demonstrating lifecycle configuration through concrete application resources.
What you can do after
Operate/configure deployment lifecycle monitoring with Kubernetes annotations and pre- or post-deployment TaskDefinitions.
How it connects
Connects Kubernetes Scheduler, deployment observability, Kubernetes annotations, lifecycle hooks, and deployment checks.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Platform Engineering on Kubernetes. The section links point to the parts of the book it draws on.