-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KEP 168: Visibility for cluster queue #1069
Conversation
Hi @stuton. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
/assign |
/ok-to-test |
84205b9
to
cd06b83
Compare
/assign |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, minor naming nits
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some recommendations that can be done as follow ups or now
/hold
/approve
} | ||
} | ||
|
||
var DefaultOptions = ClusterQueueReconcilerOptions{} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it need to be exported?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does not need to be exported. But there is a collision with another defaultOptions
in the package. We can rename it to defaultCqOptions
. Ticketed: #1100
return cq.Status.PendingWorkloadsStatus | ||
} | ||
|
||
func (r *ClusterQueueReconciler) Start(ctx context.Context) error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what calls this function? Is it internally called within SetupWithManager
?
It feels a bit like an overload to make the Reconciler also be the one that calls the reconciler? If possible, I would split it into its own struct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have traced this a little. The clusterqueue_controller.Start
is called from here: https://github.com/kubernetes-sigs/controller-runtime/blob/2a553d6f910dfc4b0796142ba1e059639a21c54a/pkg/manager/runnable_group.go#L223C17-L223C22.
So, the Start
is registered in the runnable Other
group here, and Started here: https://github.com/kubernetes-sigs/controller-runtime/blob/2a553d6f910dfc4b0796142ba1e059639a21c54a/pkg/manager/internal.go#L417.
The start we call from within Kueue:
Line 175 in 330505e
if err := mgr.Start(ctx); err != nil { |
So calling SetupWithManager
does not call directly the Start
, but registers the runnable.
I see, seems possible. There could be something like ClusterQueueSnapshotManager
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ticketed: #1099
} | ||
for _, e := range c.inadmissibleWorkloads { | ||
elements = append(elements, e) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could we release the lock at this point?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the sorting can be done outside the lock.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ticketed as: #1098
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, stuton 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:
Approvers can indicate their approval by writing |
All are good points, but I think it will be better to do follow ups as @stuton is taking a week off, so waiting with the PR would risk solving merge conflicts. |
xref: #1098 |
/hold cancel |
/test pull-kueue-verify-main |
@tenzen-y it's an omission. Would you like to create an issue to follow up? |
Yes, I prefer to disable this feature as a default since this feature seems to be a bit aggressive. Any thought? > @alculquicondor |
Sure thing, let's put it under a feature gate. |
Created: #1102 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
First iteration: support visibility for ClusterQueues
Which issue(s) this PR fixes:
Part of #168
Special notes for your reviewer:
Does this PR introduce a user-facing change?