Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-4434

Continuously generating secrets in the TempoStack instance namespace on OCP 4.16

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Blocker Blocker
    • None
    • None
    • None
    • None
    • Tracing Sprint # 256

      Version of components:

      tempo-operator.v0.10.0-7

      OpenShift version  4.16.1

      Description of the problem:
      When a TempoStack instance is created on OpenShift version 4.16, we see a perpetual creation of secrets in the namespace. Around 15-20 secrets are created per second. We need to get this fixed as soon as possible as it can overwhelm the API server causing the cluster to be instable. 

      tempo-simplest-distributor-mtls      kubernetes.io/tls         2      2m23s
      tempo-simplest-dockercfg-222jl       kubernetes.io/dockercfg   1      9s
      tempo-simplest-dockercfg-24s9w       kubernetes.io/dockercfg   1      32s
      tempo-simplest-dockercfg-256ql       kubernetes.io/dockercfg   1      78s
      
      
      i% oc get secrets| wc -l
           852
      % oc get secrets| wc -l
           864
      % oc get secrets| wc -l
           882
      % oc get secrets| wc -l
           892
      

      Steps to reproduce the issue:

      • Deploy a OpenShift 4.16 cluster.
      • Create a TempoStack instance.
      • Check the TempoStack instance namespace for the secrets.
      • Notice that the secrets are continuously being generated. 

      Additional details:
      The issue occurs on OpenShift version 4.16 only. 

       

            rvargasp@redhat.com Ruben Vargas Palma
            rhn-support-ikanse Ishwar Kanse
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: