Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-2240

Operator CLBO when failing to discover some APIs

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • netobserv-1.9
    • netobserv-1.8
    • Operator
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • NetObserv - Sprint 271, NetObserv - Sprint 272
    • None
    • None
    • Hide
      Previously, when the operator checked for available Kubernetes APIs in order to adapt its behaviour, if there was a stale API, this would result in an error, that prevented the operator to start normally. With this patch, the operator will ignore errors on unrelated APIs, will log errors on related APIs, and will continue to run normally.
      Show
      Previously, when the operator checked for available Kubernetes APIs in order to adapt its behaviour, if there was a stale API, this would result in an error, that prevented the operator to start normally. With this patch, the operator will ignore errors on unrelated APIs, will log errors on related APIs, and will continue to run normally.

      The problem is seen when, if you run "kubectl get apiservice", you see some unavailable APIs. So, in order to reproduce, you must find a way to have an unavailable API.

      E.g:

      oc scale deployments/metrics-server  -n openshift-monitoring --replicas=0 

       

      Then, install netobserv operator.

      Operator would be in CLBO...

       

      See upstream issue: https://github.com/netobserv/network-observability-operator/issues/1473

      And my suggestion: https://github.com/netobserv/network-observability-operator/issues/1473#issuecomment-2847099786

              jtakvori Joel Takvorian
              jtakvori Joel Takvorian
              None
              None
              None
              Mehul Modi Mehul Modi
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: