plState := cfgCtlr.priorityLevelStates[plName]. It may not exist and the plState may be nil。

[tm-worker]

kubernetes/staging/src/k8s.io/apiserver/pkg/util/flowcontrol/apf_controller.go

Line 1009 in ad18954

plState := cfgCtlr.priorityLevelStates[plName]

[tm-worker]

/sig apiserver

[k8s-ci-robot]

@tm-worker: The label(s) sig/apiserver cannot be applied, because the repository doesn't have them.

In response to this:

/sig apiserver

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.

[tm-worker]

/sig area/apiserver

[k8s-ci-robot]

@tm-worker: The label(s) sig/area/apiserver cannot be applied, because the repository doesn't have them.

In response to this:

/sig area/apiserver

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.

[tm-worker]

area/apiserver

[xxwwbb3]

area/apiserver

[tm-worker]

/sig/area/apiserver

[xxwwbb3]

/area apiserver

[tm-worker]

/kind bug

[kannon92]

/sig api-machinery

[fedebongio]

This is Priority and Fairness, so assigning people accordingly to take a look:
/assign @MikeSpreitzer @tkashem @lavalamp
/triage accepted

[lavalamp]

Can you share a stack trace or something? This isn't much to go on.

[tm-worker]

Can you share a stack trace or something? This isn't much to go on.

There was no nil check when using plState. but why ?

[MikeSpreitzer]

Because https://github.com/kubernetes/kubernetes/blob/ad18954259eae3db51bac2274ed4ca7304b923c4/staging/src/k8s.io/apiserver/pkg/util/flowcontrol/apf_controller.go#L728C2-L730, and the ensuring that the mandatory priority levels are represented, makes sure that only extant priority levels are referenced.

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[fedebongio]

/triage accepted