Commands icon
If icon
SlackIncomingWebhook icon
Schedule icon

Kubernetes cert-manager ACME Order Failure and Ingress TLS Sentinel

Audits Kubernetes cert-manager certificates and ACME orders to detect certificate issuance failures before domain TLS expiration.

Categories
CloudInfrastructure

How it works

This workflow queries cert-manager.io Custom Resource Definitions (certificates and orders) across all cluster namespaces using kubectl. It checks for ACME orders stuck in errored or invalid states, as well as certificates where the Ready condition is not True. If failures exceed the specified threshold, an immediate incident alert is pushed to Slack with relevant namespaces and failure reasons.

What you get

  • Real-time detection of Let's Encrypt / ACME challenge failures (DNS-01, HTTP-01).
  • Prevents catastrophic ingress certificate expiration outages.
  • Consolidated failure reporting across multi-tenant cluster namespaces.

Who it's for

  • Security Engineers and SREs managing automated public TLS certificates across Kubernetes ingresses.
  • DevOps teams maintaining microservices exposed over HTTPS.

Why orchestrate this with Kestra

  • Proactive Remediation: Catch failed renewal attempts 30 days prior to certificate expiration instead of discovering browser security warnings in production.
  • Robust Error Handling: Dedicated execution guards catch API outages or missing CRDs cleanly.
  • Zero Infrastructure Footprint: Executes cleanly inside lightweight Kubernetes runner containers.

Prerequisites

  • cert-manager installed in the cluster with certificates.cert-manager.io and orders.acme.cert-manager.io CRDs.
  • Cluster credentials with read access to cert-manager CRDs.
  • Secret SLACK_WEBHOOK configured in Kestra.

Quick start

  1. Import this blueprint into Kestra.
  2. Provide your SLACK_WEBHOOK secret.
  3. Run the workflow to verify certificate health across all ingress controllers.

How to extend

  • Trigger an automated cert-manager pod restart or re-issue annotation upon prolonged challenge failures.
  • Integrate with DNS provider monitoring to correlate DNS-01 API rate limits.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.