-
Notifications
You must be signed in to change notification settings - Fork 464
Rename ClusterProfileConfig to ClusterProfile #7785
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
Rename ClusterProfileConfig to ClusterProfile #7785
Conversation
in the Config API for MultiKueue
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @hdp617. Thanks for your PR. I'm waiting for a github.com 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-sigs/prow repository. |
|
/lgtm |
|
LGTM label has been added. Git tree hash: fa4c2cc3f615eb320f375fbea3455eb758dd3352
|
tenzen-y
left a comment
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 👍
Thank you!
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hdp617, mimowo, tenzen-y 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 |
|
/ok-to-test |
|
/test pull-kueue-test-e2e-tas-main Install errors: |
in the Config API for MultiKueue
What type of PR is this?
/kind cleanup
/kind api-change
What this PR does / why we need it:
Rename ClusterProfileConfig to ClusterProfile.
Which issue(s) this PR fixes:
Special notes for your reviewer:
This addresses the following comments in PR #7570.
Does this PR introduce a user-facing change?