Skip to content
antalos

cert-manager · Use

cert-manager automates TLS certificate issuance and renewal. Application owners declare a Certificate and reference its generated TLS Secret from ingress. antalos uses DNS-01 validation through Cloudflare and the letsencrypt-prod ClusterIssuer.

Access and audience

This is a platform service with no standalone user-facing website. Its consumers use Kubernetes resources or internal endpoints.

Your first workflow

  1. Keep one certificate.yaml with each TLS-enabled service. List every DNS name served by that certificate.

  2. Reference the generated Secret in the service’s ingress and keep the certificate in the namespace that consumes it.

  3. Use certificate status and ACME challenge events to understand issuance. A browser receiving an old certificate may still be reaching the wrong ingress route.

Get help

Report the service hostname, certificate error, and time. Do not bypass the warning or change device trust settings to hide an unexpected certificate problem.

During an interruption

An interruption can affect the applications that depend on this platform service. Ask the administrator to identify the affected service and expected recovery path.

Administrators can read the architecture and recovery limits.

Official documentation

Use the official cert-manager documentation for the complete feature reference. Some features depend on the installed version and options. If the manual differs from what you see, ask your administrator which version and features are enabled.

For antalos-specific state and availability, continue to Infrastructure Explanation. For installation and integration setup, use Deployment and Admin Guide.