Uploaded image for project: 'OpenShift Workloads'
  1. OpenShift Workloads
  2. WRKLDS-374

Descheduler as default operator in OCP

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • Descheduler as default operator in OCP
    • False
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      today De scheduler is delivered as an optional operator . This EPIC is to make de scheduler operator as a ship and installed from day1 in openshift . 

      We will provide admin a tool ( either CLI or UI) where they can visualize or simulate the recommendation . Admin will have ability to select from following option

      1. Manual mode : De scheduler will do nothing
      2. Partially automated mode : De scheduler will make recommendations and admin will perform action
      3. Automatic : Descheduler will perform the action without admin intervention 

      As an openshift admin some time i notice that pod's are scheduled on wrong nodes due to dynamic nature of K8 . i want a k8 feature that is installed and run as default with the cluster that can keep watch on those rouge pods and evict them so that my pod resources are balance out in the cluster.

      Acceptance Criteria

      • descheduler operator 4.13 is installed by CVO
      • descheduler operator 4.13 is no longer available through the operator hub
      • descheduler operator CVO installation replaces the operator hub installation

          1.
          Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          QE Tracker Sub-task Closed Undefined Unassigned
          3.
          TE Tracker Sub-task Closed Undefined Unassigned

              jchaloup@redhat.com Jan Chaloupka
              gausingh@redhat.com Gaurav Singh
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: