You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
when a multiKueueCluster is created, the function named queueReconcileForConfigUsers is used directly in admissioncheck.go#L270
What you expected to happen:
the function named queue(admissioncheck.go#L313) should be used, then the function named queueReconcileForConfigUsers used in queue function.
How to reproduce it (as minimally and precisely as possible):
when a multiKueueCluster is created
What happened:
when a multiKueueCluster is created, the function named queueReconcileForConfigUsers is used directly in admissioncheck.go#L270
What you expected to happen:
the function named queue(admissioncheck.go#L313) should be used, then the function named queueReconcileForConfigUsers used in queue function.
How to reproduce it (as minimally and precisely as possible):
when a multiKueueCluster is created
Anything else we need to know?:
kueue/pkg/controller/admissionchecks/multikueue/admissioncheck.go
Lines 264 to 273 in 43e5eb8
Environment:
kubectl version
):git describe --tags --dirty --always
):cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: