Skip to content
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

Orphan ClusterRole resource-metrics-server-resources deployed #675

Open
zyue110026 opened this issue Aug 1, 2024 · 1 comment · May be fixed by #676
Open

Orphan ClusterRole resource-metrics-server-resources deployed #675

zyue110026 opened this issue Aug 1, 2024 · 1 comment · May be fixed by #676
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@zyue110026
Copy link

We have noticed an instance of an orphan resource in one of your Kubernetes configuration files. Deploying Kubernetes resources that are not being actively used or referenced by any other resources in the cluster can lead to orphan resources. These orphan resources consume unnecessary resources and can potentially cause confusion or clutter within the cluster. Additionally, we provide anecdotal evidence from topolvm-topolvm#484 regarding the orphan resource defect.

What happened?:

ClusterRole resource-metrics-server-resources does not have any cluster role binding.

What did you expect to happen?:

resource-metrics-server-resources role should have a role binding, otherwise it is a orphan resource. Or delete resource-metrics-server-resources to avoid deploy orphan resource.

Anything else we need to know?:

Environment:

  • prometheus-adapter version: master branch
  • prometheus version:
  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • Other info:
@zyue110026 zyue110026 added the kind/bug Categorizes issue or PR as related to a bug. label Aug 1, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 1, 2024
@dgrisonnet
Copy link
Member

/assign @zyue110026
/triage accepted

@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 Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants