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

Ignore non-ready endpoints when processing endpointslices

    XMLWordPrintable

Details

    • Moderate
    • SDN Sprint 227
    • 1
    • Approved
    • False
    • Hide

      None

      Show
      None

    Description

      This is a clone of issue OCPBUGS-1427. The following is the description of the original issue:
      —
      Description of problem:

      Jump looks the worst on gcp, but looking closer Azure and AWS both jumped as well just not as high.

      Disruption data indicates that the image registry on GCP was averaging around 30-40 seconds of disruption during an upgrade, until Aug 27th when it jumped to 125-135 seconds and has remained there ever since.

      We see similar spikes in ingress-to-console and ingress-to-oauth. NOTE: image registry backend is also behind ingress, so all three are ingress related disruption.

      https://datastudio.google.com/s/uBC4zuBFdTE

      These charts show the problem on Aug 27 for registry, ingress to console, and ingress to oauth.

      sdn network type appears unaffected.

      Something merged Aug 26-27 that caused a significant change for anything behind ingress using ovn on gcp.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1427 Ignore non-ready endpoints when processing endpointslices

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1427 Ignore non-ready endpoints when processing endpointslices

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is depended on by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-2554 ingress, authentication and console operator goes to degraded after switching default application router scope

          • 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
          links to

          GitHub openshift/ovn-kubernetes#1344: [release-4.12] OCPBUGS-3003: Ignore non-ready endpoints when processing endpointslices

          Activity

            People

              rravaiol@redhat.com Riccardo Ravaioli
              openshift-crt-jira-prow OpenShift Prow Bot
              Anurag Saxena Anurag Saxena
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: