Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-1098

Setting a telemeter proxy in the cluster-monitoring-config config map does not work as expected

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Normal
    • None
    • 4.12.0
    • Monitoring
    • ?
    • Low
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      Setting a telemeter proxy in the cluster-monitoring-config config map does not work as expected

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:
      the following KCS details steps to add a proxy.
      The steps have been verified at 4.7 but do not work at 4.8, 4.9 or 4.10

      https://access.redhat.com/solutions/6172402

      When testing at 4.8, 4.9 and 4.10 the proxy setting where also nested under `telemeterClient`

      which triggered a telemeter restart but the proxy setting do not get set in the deployment as they do in 4.7

      Actual results:

      4.8, 4.9 and 4.10 without the nested `telemeterClient`
      does not trigger a restart of the telemeter pod

      Expected results:

      I think the proxy setting should be nested under telemeterClient
      but should set the environment variables in the deployment

      Additional info:

      Attachments

        Issue Links

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: OCPBUGS

              People

                jrodrig@redhat.com Juan Rodriguez Hortala (Inactive)
                jrodrig@redhat.com Juan Rodriguez Hortala (Inactive)
                Junqi Zhao Junqi Zhao
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: