Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-7519

Add "terminated-pod-gc-threshold" as a configurable parameter in the KubeControlManager operator

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • 4.16, 4.18, 4.17
    • kube-apiserver
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      • Proposed title of this feature request
        Add "terminated-pod-gc-threshold" as a configurable parameter in the KubeControlManager operator
      • What is the nature and description of the request?
        In some cases the pods may be evicted and the terminated pods remained in ContainerStatusUnknown state.

      We need configurable parameter In KCM so that we can tune this default number which is huge by default. 12500, which is relatively big especially for the SNO(Single Node OpenShift) which may give the feeling that the terminated pods remained in the cluster and won't be cleanup for ever.

              racedoro@redhat.com Ramon Acedo
              rhn-support-nbhatt Neeraj Bhatt
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved:
                None
                None