This represents the OSSM side of OSSMDOC-266.

The operator abstracts away the configmaps and updates them on reinstall of the control plane. Currently we advise users to update the control plane to enable policy checks rather than updating the SMCP. This would mean that the operator may remove those changes on a reinstall/reconciliation.

Here is where we do it in Maistra: maistra.io/docs/troubleshooting/troubleshooting_policy
Here is where we do it in OSSM: docs.openshift.com/container-platform/3.11/servicemesh-install/servicemesh-install.html#update-mixer-policy-enforcement

(More current link to the topic -> docs.openshift.com/container-platform/4.7/service_mesh/v1x/prepare-to-deploy-applications-ossm.html#ossm-mixer-policy-1x_deploying-applications-ossm-v1x )