kube-scheduler-wasm-extension icon indicating copy to clipboard operation
kube-scheduler-wasm-extension copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Add RunFilterPluginsWithNominatedPods

Open chansuke opened this issue 7 months ago • 4 comments

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

What are the benchmark results of this change?

chansuke avatar Apr 20 '25 16:04 chansuke

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: chansuke Once this PR has been reviewed and has the lgtm label, please assign codefromthecrypt for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

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 avatar Apr 20 '25 16:04 k8s-ci-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

k8s-triage-robot avatar Aug 08 '25 03:08 k8s-triage-robot

/remove-lifecycle stale

sanposhiho avatar Aug 16 '25 05:08 sanposhiho

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

k8s-triage-robot avatar Nov 14 '25 05:11 k8s-triage-robot