You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
Other debugging information (if applicable):
$ kubectl logs
The text was updated successfully, but these errors were encountered: