How to avoid auto generated secrets removal during upgrade from OpenShift 4.14 to 4.15

Solution Verified - Updated -

Issue

  • Starting with Red Hat OpenShift Container Platform 4.15, if the internal Image Registry is disabled (i.e., configured with the Removed management state), the ServiceAccount token Secrets used for authentication with the internal Image Registry are no longer automatically generated, and if the Image Registry was previously enabled (i.e., configured with the Managed management state) the previously automatically generated ServiceAccount token Secrets are automatically deleted.

  • Is it possible to preserve auto-generated legacy ServiceAccount token Secrets during an upgrade to OpenShift 4.15 when the internal Image Registry is disabled?

Environment

  • Red Hat Openshift Container Platform (RHOCP)
    • 4.14
    • 4.15
  • Disabled OpenShift internal Image Registry

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content