Wei
because of security problem, I prefer dispathcer only works in one namespace.
https://docs.google.com/document/d/1q3kkBhSqWMHm-TCFo56R-32C7-fo6G8KQH4lIGtc-U0/edit?usp=sharing here is the first proposal, If the way is right, I will do more details design. cc @julz @mattmoor
hi, @lizzzcai, the only way to support path based routing is using VirtualService for now(like what u do now). I am wondering whether to support routing to multi-namespace. But there...
cc @mattmoor @julz
@lookis Still in proposal, what is your usecase?
cc @nader-ziada
So let's push this forward, referring to the meeting notes before, the best way is to add a labels to decide whether to sync the ns: my first think is...
And also, referring other famous projects, the labels should follow: `submodel.karmada.io/(resource or config): xxx`
`controller.karmada.io/namespace-visibility`: 1. host-plane-only 2. host-only 3. control-plane-only
There is four cases: 1. create ns with `controller.karmada.io/namespace-visibility` label: so just not create work resource. 2. create ns with `controller.karmada.io/namespace-visibility `label, then patch it without label, so it will...