Major Description
1. Proposed title of this feature request
Strategic Merge in OpenShift Container Platform oauth.config.openshift.io resources (for identityProviders)
2. What is the nature and description of the request?
With OpenShift Container Platform 4, everything can be configured, using an API endpoint. This opens the possibility to manage OpenShift Container Platform with GitOps approach and use tooling such as OpenShift GitOps, kustomize or even ansible with k8s modules.
This works great and is really a massive value add. But it seems that for example in oauth.config.openshift.io the list of identityProviders can't me managed with Strategic Merge as the respective API fields are not configured accordingly
See types_oauth.go for details.
Meaning it's required to apply JSON Patch which works but is complicated and either need to be build while applying changes (using machine logic) or even manual work.
With Strategic Merge it would be possible to define all the possible identityProviders and apply them on the OpenShift Container Platform - Cluster depending on environment/stage, etc. without additional effort. So each definition could be managed as a single identityProviders or be merged to provide multiple identityProviders.
3. Why does the customer need this? (List the business requirements here)
identityProviders in types_oauth.go allows to add a lit of identityProviders and it's therefore possible that at one point in time identityProviders A will be applied and used. But potentially when on boarding additional customers, it may be required to add identityProviders B and this should be possible with a Strategic Merge patch and not a rather complex JSON Patch that may just work with a set of OpenShift Container Platform - Cluster but not all of them.
4. List any affected packages or components.
OpenShift Container Platform - oAuth configuration (types_oauth.go)
