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.
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.
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:
kubectl version
):