Skip to content

Fix: Use metric server full name instead of name for clusterrole in helm chart#1801

Open
yesdeepakverma wants to merge 1 commit into
kubernetes-sigs:masterfrom
yesdeepakverma:aggregate-cluster-role
Open

Fix: Use metric server full name instead of name for clusterrole in helm chart#1801
yesdeepakverma wants to merge 1 commit into
kubernetes-sigs:masterfrom
yesdeepakverma:aggregate-cluster-role

Conversation

@yesdeepakverma

Copy link
Copy Markdown

**This PR fixes the cluster role name to use helm chart full name instead of just the name which is default to metric-server **:

Almost all the resource except the APIService resource uses the (include "metrics-server.fullname" .) to generate the resources names . The cluster in fix is only used to be aggregated to upstream admin/edit/viewer role as per the annotation specified in the cluster role.
As per https://github.com/kubernetes/kubernetes/blob/master/plugin/pkg/auth/authorizer/rbac/bootstrappolicy/policy.go#L375 and https://github.com/kubernetes/kubernetes/blob/master/plugin/pkg/auth/authorizer/rbac/bootstrappolicy/policy.go#L396 and https://github.com/kubernetes/kubernetes/blob/master/plugin/pkg/auth/authorizer/rbac/bootstrappolicy/policy.go#L386, any role having these annotation will be aggregated to admin/edit/view role

Fixes #

  1. Use the fullname instead of name for cluster role .

This fix will help using the same naming convention as other resources in helm chart. This further will help users who have been managing the metric-server chart locally and wants to switch to upstream public helm chart for metric server. this will helm then install the helm chart without uninstalling the metric server chart first .

helm template command used to generate before and after the changes:

helm template my-release ./metrics-server

image

@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yesdeepakverma
Once this PR has been reviewed and has the lgtm label, please assign stevehipwell for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@linux-foundation-easycla

linux-foundation-easycla Bot commented May 30, 2026

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: yesdeepakverma / name: Deepak Verma (7a3c3ca)

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels May 30, 2026
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

Welcome @yesdeepakverma!

It looks like this is your first PR to kubernetes-sigs/metrics-server 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/metrics-server has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot

Copy link
Copy Markdown
Contributor

Hi @yesdeepakverma. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 30, 2026
@github-project-automation github-project-automation Bot moved this to Needs Triage in SIG Instrumentation May 30, 2026
@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels May 30, 2026
@yangjunmyfm192085

Copy link
Copy Markdown
Contributor

/ok-to-test
/cc @stevehipwell

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 2, 2026
@yangjunmyfm192085

Copy link
Copy Markdown
Contributor

/retest

@dgrisonnet

Copy link
Copy Markdown
Member

/triage accepted
/assign @stevehipwell

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 4, 2026
@yesdeepakverma

Copy link
Copy Markdown
Author

Looking for feedback. Let me know if something is required from my side.

@yesdeepakverma

Copy link
Copy Markdown
Author

Hi @stevehipwell - please take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

5 participants