update extension point PostFilter comment

[goofy-z]

What type of PR is this?

/sig scheduling
/kind documentation

What this PR does / why we need it:

According to [KEP]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/624-scheduling-framework#postfilter

PostFilter Plugins are called after Filter phase, but only when no feasible nodes were found for the pod

Also I found the code:

kubernetes/pkg/scheduler/scheduler.go

Lines 455 to 469 in 80056f7

	if fitError, ok := err.(*framework.FitError); ok {
	if !fwk.HasPostFilterPlugins() {
	klog.V(3).InfoS("No PostFilter plugins are registered, so no preemption will be performed")
	} else {
	// Run PostFilter plugins to try to make the pod schedulable in a future scheduling cycle.
	result, status := fwk.RunPostFilterPlugins(ctx, state, pod, fitError.Diagnosis.NodeToStatusMap)
	if status.Code() == framework.Error {
	klog.ErrorS(nil, "Status after running PostFilter plugins for pod", "pod", klog.KObj(pod), "status", status)
	} else {
	klog.V(5).InfoS("Status after running PostFilter plugins for pod", "pod", klog.KObj(pod), "status", status)
	}
	if status.IsSuccess() && result != nil {
	nominatedNode = result.NominatedNodeName
	}
	}

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

[k8s-ci-robot]

@goofy-z: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-ci-robot]

Hi @goofy-z. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[goofy-z]

😂 maybe it's a wrong pr, can someone review this

[goofy-z]

/assign

[ahg-g]

/ok-to-test
/label api-review
/lgtm

This was missed when when changed the semantics of PreFilter in the alpha phase.

[liggitt]

docs only change, deferring to scheduler reviewer

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: goofy-z, liggitt

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

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/scheduler/apis/config/OWNERS [liggitt]
• staging/src/k8s.io/kube-scheduler/config/OWNERS [liggitt]

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

[goofy-z]

/retest