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

Set shutdown watch termination grace period on kube-apiserver

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • 4.18.0
    • 4.18.z
    • HyperShift
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      *Cause*: Default behavior
      *Consequence*: watch termination grace period on kube-apiserver is not set
      *Fix*: Ensure kube-apiserver watch termination grace period is set to 25s
      *Result*: Bug isn't present anymore.
      Show
      *Cause*: Default behavior *Consequence*: watch termination grace period on kube-apiserver is not set *Fix*: Ensure kube-apiserver watch termination grace period is set to 25s *Result*: Bug isn't present anymore.
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-52424. The following is the description of the original issue:

      Description of problem:

          Set the `shutdown-watch-termination-grace-period` set for `kube-apiserver` on Hypershift managed clusters

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

          

      How reproducible:

          

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

              jared.hayes Jared Hayes (Inactive)
              openshift-crt-jira-prow OpenShift Prow Bot
              Wen Wang Wen Wang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: