d1. Proposed title of this feature request
Cache /.well-known/openid-configuration for some time when OpenID Connect identity provider is configured to prevent too many queries towards /.well-known/openid-configuration

2. What is the nature and description of the request?
Based on https://github.com/openshift/cluster-authentication-operator/pull/99 we are querying /.well-known/openid-configuration during every reconcile loop of the authentication-operator when OpenID Connect identity provider is configured as we are fetching configuration information for OpenID Connect identity provider. While this is nice it adds a lot of load on the OpenID Connect infrastructure especially if many OpenShift Container Platform - Cluster is running. It therefore would be good to cache the results for some time and avoid a query towards /.well-known/openid-configuration during every reconcile loop as also information in /.well-known/openid-configuration are rather static.

3. Why does the customer need this? (List the business requirements here)
With many OpenShift Container Platform - Cluster there will be many call towards /.well-known/openid-configuration which can add unexpected load onto OpenID Connect infrastructure. This is why it was requested to cache the information from /.well-known/openid-configuration for some time reduce the overall number of queries from all OpenShift Container Platform - Cluster.

4. List any affected packages or components.
authentication-operator