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

Changes to spec.meshconfig are not picked up immediately


    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • OSSM 2.0.8, OSSM 2.1.1
    • Maistra
    • None
    • False
    • False

      Currently, when making a change to spec.meshconfig that influences e.g. sidecar injection, those changes are not immediately applied, because istiod does not watch the ConfigMap for changes. When users edit meshconfig in the SMCP, they still have to manually do

      kubectl rollout restart deployment istiod

      to apply their new meshconfig.

      We should look into automating this- we're offering an operator after all, so we can react to changes in the ConfigMap. The simplest way would be to add an annotation to the istiod pod that holds the SHA256 of the relevant ConfigMaps, as described in the helm docs: Automatically Roll Deployments.

            Unassigned Unassigned
            dgrimm@redhat.com Daniel Grimm
            0 Vote for this issue
            2 Start watching this issue