Goal:

As an OpenShift user, I would like to upgrade one or many clusters, by applying a locally managed ClusterVersion resource, following the approach mentioned in https://kubernetes.io/docs/tasks/manage-kubernetes-objects/declarative-config/

oc get clusterversion/version -o yaml > cluster_version.yaml
 # remove internal fields from yaml
vi cluster_version.yaml
oc replace --save clusterversion.yaml

Kubernetes resource management via Declarative Config instead of imperative configs is recommended in the book Kubernetes Up and Running.

Business Justification
This RFE would allow declarative management of cluster upgrades via `oc apply -f` for multiple clusters, and manage with ArgoCD the ClusterVersion object, ignoring irrelevant fields using https://argo-cd.readthedocs.io/en/stable/user-guide/diffing/#application-level-configuration.

Acceptance Criteria
For this we would need to reword, removing or rename the statement in https://docs.openshift.com/container-platform/4.7/post_installation_configuration/cluster-tasks.html#informational-resources_post-install-cluster-tasks

In OpenShift Container Platform 4.7, you must not customize the ClusterVersion resource for production clusters. Instead, follow the process to update a cluster,  (link to oc adm upgrade)