In OCP 4.15, if the Image Registry is set to `removed`, the automatically created serviceAccount token secrets are deleted.
While those should be only used to access the internal Image Registry, there are several customers using them for custom workloads, causing them issues and outages after upgrading from 4.14 to 4.15 with the Image Registry removed

Upgrades from 4.14 to 4.15

Always

    1. Install a 4.14 cluster.
    2. Use any of the automatically generated "token-xxxx" secrets for any puropose
    3. Set the Image Registry as `removed`.
    4. Upgrade the cluster to 4.15, and anything using the above token will fail.
    

Anything using the secrets created in 4.14 will fail.

If the Image Registry is `removed` in the cluster, an ACK similar to the ones for the API removals should be added, to require customers with the Image Registry `removed` to check if they are using the any of the `secrets` that are going to be removed with the upgrade to 4.15.

Only if the Image Registry is `removed` in the cluster.