Blog Post

Azure Arc Blog
3 MIN READ

Introducing cert-manager for Azure Arc-enabled Kubernetes: now in Public Preview

NicolasMondada's avatar
May 06, 2026

Today we’re releasing a public preview of cert-manager for Azure Arc-enabled Kubernetes. It’s an Arc extension that automates TLS certificate and trust bundle management for edge Kubernetes clusters. 

If you’re running Kubernetes at the edge: in factories, retail stores, remote sites, you’ve probably hit the certificate problem already. Certificates expire. Each cluster has its own tooling. Nobody owns the renewal process until something breaks. We routinely hear from customers that certificate issues are a common source of unplanned outages and last-minute firefighting, especially as workload counts grow. 

This extension packages the open-source cert-manager and trust-manager into a managed Arc extension with Microsoft support. You get automated lifecycle management and trust distribution without having to run and maintain these tools yourself. 

What it does 

The extension bundles two CNCF-graduated projects: cert-manager and trust-manager, into a single Arc-K8s extension that you install once per cluster. From there: 

1. You can issue, renew, and rotate certificates automatically. You do not need to manage them manually. 

2. You can distribute trusted CA certificates consistently across namespaces. No more per-workload trust configuration.

3. You choose the CA issuer: built-in self-signed for dev/test, or your enterprise PKI for production. 

4. The extension ships with enterprise support, regular security patches, and proactive maintenance from Microsoft team. 

Why we built it 

We built Microsoft cert-manager for Azure Arc-enabled Kubernetes to address three recurring problems we saw in real hybrid and edge environments. 

Problem 1: Manual certificate issuance. 

Many organisations still issue, install, and renew certificates through manual steps across clusters and namespaces. That creates operational overhead, slows teams down, and increases the risk of outages when certificates expire or are configured incorrectly. 

The answer is automation. With cert-manager running as an Arc-enabled extension, teams can automate certificate issuance, renewal, and rotation through Kubernetes-native workflows instead of relying on tickets, scripts, and manual intervention. 

Problem 2: Fragmented approaches to automation. 

Even when teams try to automate, they often end up with a mix of scripts, custom controllers, product-specific setups, and one-off operational patterns. That fragmentation makes certificate management harder to scale, harder to standardise, and harder to operate consistently across environments. 

The answer is to standardise on cert-manager. It provides a common, Kubernetes-native approach to certificate lifecycle management, helping teams reduce tool sprawl, align on a consistent operating model, and simplify how certificates are managed across clusters. 

Problem 3: Maintenance and upgrade burden for open-source cert-manager. 

cert-manager is a powerful open-source project, but many organisations do not want the ongoing burden of packaging, validating, patching, upgrading, and supporting it themselves as a production dependency. That can create operational risk, delay updates, and make long-term ownership unclear. 

The answer is a Microsoft-supported Arc-enabled extension. Microsoft cert-manager for Azure Arc-enabled Kubernetes gives customers a supported way to use cert-manager, with Microsoft handling packaging, delivery, and ongoing maintenance so teams can adopt the capability without taking on the full operational burden of managing the OSS component themselves.

What’s in the public preview 

Here’s what you get: 

  1. Certificate lifecycle automation with cert-manager: issuance, renewal, rotation, all handled for you. 
  2. Trust bundle distribution with trust-manager: push trusted CA certs to every namespace that needs them. 
  3. Self-signed or external CA. Start with the built-in CA, swap in your enterprise PKI when you’re ready. 
  4. Secure by default. We turned on the security settings you’d want enabled anyway: TLS enforcement, least-privilege RBAC, restricted pod security. 
  5. Tested at the edge. Validated on AKS Edge Essentials, AKS on Azure Local, and several third-party Kubernetes distros. Works offline. 

Fits into your Arc stack 

If you’re already running Azure IoT Operations or Azure Monitor on Arc-enabled clusters, the extension handles TLS between those services with minimal setup. No custom certificate plumbing required: install the extension and the other Arc components pick it up. 

Get started 

The extension is available now in public preview. 

👉 Documentation and quickstart 

Updated May 12, 2026
Version 3.0
No CommentsBe the first to comment