Red Hat OpenShift uses TLS certificates across many platform components to establish trust and secure communications. As platforms grow and evolve over years of operation, managing these certificates consistently becomes increasingly difficult. For years, Red Hat and NEC have worked together to understand and address certificate management challenges in Red Hat OpenShift. Through that collaboration, TLS Registry emerged as a mechanism to make certificate management observable and verifiable across the platform.
TLS Registry is integrated into Red Hat OpenShift engineering workflows to detect certificate management gaps before they become production issues. A production Red Hat OpenShift platform is expected to operate continuously for years. During that time, new operators, platform services, and workloads are introduced. Certificates expire, are renewed or replaced, and may be reissued under new certificate authorities (CAs). Like many modern distributed systems, Red Hat OpenShift relies on TLS not only for externally exposed services but also for secure communication between internal platform components.
Because Red Hat OpenShift integrates a broad set of platform services and operators, these trust relationships extend across many independently managed components. Our analysis of Red Hat OpenShift components identified more than 200 certificates and related TLS artifacts. These artifacts are stored in different locations, managed by different components, and renewed or reloaded through different procedures. Managing certificates independently within each component may work locally, but it may not work reliably to track ownership, dependencies, or the impact of changes across the platform.
As a result, seemingly simple questions become increasingly difficult to answer: These questions may remain unanswered until a certificate expires, a transition to a new CA occurs, or a platform upgrade reveals previously unknown certificate dependencies. Without a shared view of certificate ownership and trust relationships, component developers, reviewers, and release engineers lack the information needed to apply certificate management requirements consistently. It also becomes difficult to determine how a change in one component may affect other components across the platform.
