[Feature] It's not easy to filter kuberay components in Kubernetes

[Jeffwan]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

Currently, we tag kuberay deployment with label control-plane=kuberay-operator, control-plane=kuberay-apiserver.

Name:                   kuberay-apiserver
Namespace:              ray-system
CreationTimestamp:      Tue, 05 Jul 2022 10:21:35 -0700
Labels:                 control-plane=kuberay-apiserver
Annotations:            deployment.kubernetes.io/revision: 1
Selector:               control-plane=kuberay-apiserver

However, there's no easy way to filter all kuberay resources. It's better to give a consistent app level label that can be used to filter kuberay resources.

Use case

Operation purpose. This would be helpful especially when we deploy lots of application in single namespace and operators need to filter some pods or resources out.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[Jeffwan]

guidance: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/

app.kubernetes.io/name: kuberay
app.kubernetes.io/component: kuberay-apiserver

[DmitriGekhtman]

@Jeffwan is this good to close after #345?

[Jeffwan]

@DmitriGekhtman Yes. we can close this one