karmada-io
Is it appropriate to change `--skipped-propagating-apis` into `--managed-propagating-apis`?
What would you like to be added:
Why is this needed: It's more clear to know how many resources are managed by karmada, which is helpful to be aware of how much it has endured.
--skipped-propagating-apis is a kind of ignore list, but the --managed-propagating-apis is a kind of allowed list,
Do you mean people have to edit the configuration every time they add a new CRD?
How about Hot reload allowed list? The implementation method is open to further discussion.
which is helpful to be aware of how much it has endured
I'd like to hear more details about this requirement. We might have other solutions.
It seems like there are four ways to achieve it:
- add
--skipped-propagating-apisas params ofkarmada-controller-manager: API is not intuitive to users、lack of management、lack of visualization - managed as a
allowed listby RBAC: not intuitive to users too, somewhat tricky - add a new API: the workload involved may be a bit larger
- managed as a
allowed listin ConfigMap: similar to "add a new API" in basic principle, but not as clear as it is
So, I prefer to add a new API, which names like PropagateAPIList, then we can define the propagating-apis managed/skipped as a allow/ignore list in spec field, and we can observe how many resources are managed or how much it has endured in status field by kubectl. I favour it for its intuitive and visualization.
Is anything updated for the issue? It seems the point is how to show objects that the karmada controlled. Can we just create a default propagationpolicy and make it show all resources the karmada controlled? The pp needn't to be in effect and it doesn't need to add new API. By the way, it seems detector won't process resource objects without matched propagationpolicy, is it right?
Can we just create a default propagationpolicy and make it show all resources the karmada controlled? The pp needn't to be in effect and it doesn't need to add new API.
What's the default PropagationPolicy look like? Who is responsible for creating it and recording the resource list?
By the way, it seems detector won't process resource objects without matched propagationpolicy, is it right?
Yes, the unmatched resources will be put on a waiting list.
@RainbowMango: Closing this issue.
In response to this:
/close Please feel free to re-open it if you still need it.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
