What we have :

• 2.6 MCE documentation : https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.6/html-single/multicluster_engine/index#creating-a-cluster-proxy
• 2.7 cluster documentation : https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.7/html-single/clusters/index#creating-a-cluster-proxy

Changes needed :

We need to make it clear that post installation changes to the configuration are expected to be delivered by policies and refer to the governance documentation (and possibly the example repository https://github.com/open-cluster-management-io/policy-collection/tree/main/community for policy samples). A note detailing that install-config.yaml is only used on installation and not further down the line will help avoid some situations where the customer woudl try to do changes to their clusters through that.

The changes need to be delivered for documentation for ACM 2.6+ (see avove for links)