NamespaceIsolationPolicies may need support priority
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
**Is your enhancement request related to a problem? Please describe.**
A clear and concise description of what the enhancement is.
current, if we have two Policies that match the same namespace。 which one will take effect is not certain.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
add an `order` field in NamespaceIsolationData, to order them ,we

getPolicyByNamespace, we get the NamespaceIsolationPolicy which have the bigger order.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
Start by locating NamespaceIsolationData and the getPolicyByNamespace entry point, then trace how matching policies are currently selected. Confirm the intended meaning of a larger order value and identify the affected policy configuration and selection tests. Done means overlapping namespace policies have deterministic priority behavior and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100