Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-2849

Don't suggest modifying the configmap

XMLWordPrintable

      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: https://maistra.io/docs/troubleshooting/troubleshooting_policy/
      Here is where we do it in OSSM: https://docs.openshift.com/container-platform/3.11/servicemesh-install/servicemesh-install.html#update-mixer-policy-enforcement

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

        1.
        Maistra Updates Sub-task Closed Major Unassigned
        2.
        OSSM Updates Sub-task Closed Major Unassigned

            Unassigned Unassigned
            bravery300 Brian Avery (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: