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

Namespace/Cluster filtering #6

Open
wanghong230 opened this issue Mar 11, 2020 · 0 comments
Open

Namespace/Cluster filtering #6

wanghong230 opened this issue Mar 11, 2020 · 0 comments

Comments

@wanghong230
Copy link
Collaborator

Is this a BUG REPORT or FEATURE REQUEST?:

What happened:

We should use the native metdata lables of the CR to the cluster/namespace filitering.

For instance:

cluster/namespace will be belonging to different segment, business unit, team. Then segment, team, bu will just be the label keys. With that in mind, we don't need to add the those fields into the cluster, namespace CRD body defination.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • manager version
  • Kubernetes version :
$ kubectl version -o yaml

Other debugging information (if applicable):

- controller logs:

$ kubectl logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant