-
Notifications
You must be signed in to change notification settings - Fork 330
KueueViz to prepare for production suitable: Various renaming #4753
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
KueueViz to prepare for production suitable: Various renaming #4753
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
79a66e1
to
8823b26
Compare
@kannon92 if you can PTAL ? |
- package-ecosystem: "gomod" | ||
directories: | ||
- "/cmd/experimental/kueue-viz/backend" |
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.
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.
Keeping the main entrypoints for tooling seems to be the practice in core k8s, ptal: https://github.com/kubernetes/kubernetes/tree/master/cmd, eg kubemark
or kubeadm
, but many more.
It is also consistent with kueuectl in Kueue.
However, I would be ok to put the main body of the code under top-level kueueviz
.
Seems like kubectl
only has minimal main.go under cmd/kubectl: https://github.com/kubernetes/kubernetes/tree/master/cmd/kubectl
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.
cc @tenzen-y any opinion?
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 think this can be done in a follow up actually. I think the PR in the current form already archives the goal of moving out of experimental. and places the code next to kueuectl, so IMO this is a natural place, also given k8s convention, but Im open to move again if we conclude on a better place.
LGTM overall, just two remaining open comments. |
/kind dashboard |
8823b26
to
9bfe747
Compare
9bfe747
to
7d4a56c
Compare
/lgtm |
LGTM label has been added. Git tree hash: 6ebe6270dd615f113b2e48da9848de998ecabf62
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: akram, mimowo 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 |
7d4a56c
to
22648c2
Compare
/hold for fixing |
/unhold |
LGTM label has been added. Git tree hash: 4a9306af7489db465424d6470da870fb0c9da3a5
|
What type of PR is this?
/kind cleanup
Move KueueViz from experimental to non experimental.
Operate various renaming for consistency reasons: KueueViz is now written KueueViz without hyphen or space or camel cases.
A few exceptions:
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?