-
Notifications
You must be signed in to change notification settings - Fork 408
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 pool-coordinator to yurt-coordinator for charts #1551
rename pool-coordinator to yurt-coordinator for charts #1551
Conversation
@JameKeal: GitHub didn't allow me to assign the following users: your_reviewer. Note that only openyurtio members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
Kudos, SonarCloud Quality Gate passed!
|
Codecov Report
@@ Coverage Diff @@
## master #1551 +/- ##
=======================================
Coverage 50.85% 50.85%
=======================================
Files 133 133
Lines 15852 15852
=======================================
Hits 8062 8062
Misses 7045 7045
Partials 745 745
Flags with carried forward coverage won't be shown. Click here to find out more. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JameKeal, rambohe-ch 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 |
/lgtm |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Unify the naming rules of each component in openyurtio/openyurt repo, it is more understandable for end users.
Which issue(s) this PR fixes:
Fixes #1482
Special notes for your reviewer:
/assign @rambohe-ch
Does this PR introduce a user-facing change?
other Note