WIP: Descheduling framework PoC

[ingvagabund]

• providing PoC for Descheduler Framework Proposal #753
• the same strategy can be configured differently through different profiles: Multiple descheduler strategies of the same type #486
• following up on the v1alpha2 config: Multiple descheduler strategies of the same type #486
  Example:

  apiVersion: descheduler/v1alpha2
  kind: DeschedulerPolicy
  profiles:
  - name: ProfileName
    pluginConfig:
    - name: DomainFilter
      args:
        namespaces:
          included:
          - namespace-1
          - namespace-2
          excluded:
          - namespace-A
          - namespace-B
        labelSelector: ...
    - name: DefaultEvictor
      args:
        evictSystemCriticalPods: true # default false
        evictFailedBarePods: true # default false
        evictLocalStoragePods: true # default false
        nodeFit: true # default false
    - name: PodsHavingTooManyRestarts
      args:
        podRestartThreshold: 100
        includingInitContainers: true
    - name: LowNodeUtilization
      args:
        lowThreshold:
          cpu : 20
          memory: 20
          pods: 20
        highThreshold:
          cpu : 50
          memory: 50
          pods: 50
    - name: TopologySpreadConstraint
      args:
        includeSoftConstraints: true
    plugins:
      filter:
        # default filters: DomainFilter
        disabled:
        enabled:
      sort:
        # default sorters: Priority
        disabled:
          Priority
        enabled:
          Utilization
      deschedule:
        # plugins descheduling pods without checking other pods
        enabled:
        - PodsHavingTooManyRestarts
        - InterPodAntiAffinity
      rebalance:
        # plugins descheduling pods while balancing distribution
        enabled:
        - Duplicates
        - LowNodeUtilization
        - TopologySpreadConstraint
      evict:
        # default evict plugins: DefaultEvictor
        disabled:
          DefaultEvictor
        enabled:
          CustomEvictor

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: ingvagabund / name: Jan Chaloupka (2976e15, d0ffe8d, 9b6b266, 228b269, 58209f3, 469480a, e9bc093, c674f0a, 2c38f80)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from ingvagabund after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@ingvagabund: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[ingvagabund]

/remove-lifecycle rotten

[k8s-ci-robot]

@ingvagabund: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-descheduler-verify-master	d7745ff	link	true	/test pull-descheduler-verify-master
pull-descheduler-unit-test-master-master	d7745ff	link	true	/test pull-descheduler-unit-test-master-master
pull-descheduler-test-e2e-k8s-master-1-22	d7745ff	link	true	/test pull-descheduler-test-e2e-k8s-master-1-22
pull-descheduler-test-e2e-k8s-master-1-21	d7745ff	link	true	/test pull-descheduler-test-e2e-k8s-master-1-21
pull-descheduler-test-e2e-k8s-master-1-23	d7745ff	link	true	/test pull-descheduler-test-e2e-k8s-master-1-23
pull-descheduler-test-e2e-k8s-master-1-24	d7745ff	link	true	/test pull-descheduler-test-e2e-k8s-master-1-24
pull-descheduler-test-e2e-k8s-master-1-25	d7745ff	link	true	/test pull-descheduler-test-e2e-k8s-master-1-25
pull-descheduler-test-e2e-k8s-master-1-26	d7745ff	link	true	/test pull-descheduler-test-e2e-k8s-master-1-26

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ingvagabund]

/remove-lifecycle stale

[knelasevero]

I am closing this one 😅 I think everyone working on the framework had this saved somewhere and no need to keep this POC open :)

/close

[k8s-ci-robot]

@knelasevero: Closed this PR.

In response to this:

I am closing this one 😅 I think everyone working on the framework had this saved somewhere and no need to keep this POC open :)

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.