Uploaded image for project: 'Data Collection, Analytics, and Events'
  1. Data Collection, Analytics, and Events
  2. DCAEGEN2-1539

Traffic is not send to pod because of failed rediness probe when auth.method other than noAuth


    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Medium Medium
    • Dublin Release
    • Dublin Release
    • None
    • local staging lab

      When I change VES parameter auth.method to certOnly (only HTTPS connections available) I see a problem with failed pod rediness probe.

      Healthcheck sends get request via http, while https connection is required.

      Container with Ves Collector is marked as a Unheathly and because of that any traffic can't be send to that pod.

      Container description. Container with Ves Collector has state Ready = False  

      Pod status. 1 of 2 containers are running


      Kubernetes pod details. rediness probe failed because of refused connection.


       Additionaly Robot healthchecks got failed when flag is other than "noAuth".








            vv770d vv770d
            mprzybys mprzybys
            0 Vote for this issue
            3 Start watching this issue