openmcp-project / openmcp-project/backlog
Allow Enforced Kyverno Policies for ManagedControlPlanes
Open
Nobody has claimed this yet.
area/open-control-plane
sig/core
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Context
In the context of organizations running numerous ManagedControlPlanes, they often bring a set of unique requirements and boundaries they want to regulate possibiliteies in their MCPs.
They can changed by the org, but not by the admin of the MCP.
Acceptance Criteria
- Allow a "Project" or "Workspace" Owner, to set "manadatory Policies"
- Policies cannot be changed from within. ManagedContorlPlane
Outside of scope
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files, tests, or entry points are identified; first clarify which ManagedControlPlane and policy-management components enforce Project or Workspace Owner rules. Define how mandatory policies are represented and protected from in-plane changes, then add or identify tests proving owners can set them and MCP admins cannot override them.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100