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

Support validationMessages in SMCP

    XMLWordPrintable

Details

    • False
    • False
    • Release Notes
    • Undefined
    • Sprint 58 - week 2 and 3, Sprint 59

    Description

      Customers expect support for option "validationMessages" in SMCP. As we recently fixed issues caused by enabling this option, we could consider supporting this features and figure out scope of support and required test coverage.

      For QE:

      • OSSM operator 2.2.3 installs SMCP v2.2, so that it does not log any error as confirmed here, but SMCP v2.1 still logs errors.
      • SMCP v2.1, v2.2 and v2.3 should not log any error when are installed with the operator built from maistra-2.3 branch.

      Original title:

      validationMessages in smcp

      Original description:

      Using `validationMessages` in smcp dumps a lot of logs and istiod CPU consumption going up and evicting the pods but the customer wants to use this to see the configuration changes.

       

       

       

      Attachments

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. OSSM-1321 Enabling "validationMessages" in the SMCP causes istiod pod to log "Error writing Distribution Report: unable to create ConfigMap" twice per second

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. OSSM-2440 RPM Release for Maistra 2.1.6

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. OSSM-2488 Container release for Maistra 2.2.5

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. OSSM-2147 Unexpected validation message on Gateway object

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jewertow@redhat.com Jacek Ewertowski
              rhn-support-skanakal Siva Kanakala (Inactive)
              Prachi Yadav
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: