Skip to content

feat(namespaces): allow owners to cordon namespaces #1657

@oliverbaehler

Description

@oliverbaehler

Currently we can only cordon an entire tenant, however tenant owners should also have the power to cordon their namespaces, as they are in chaarge of them.

  1. Add a new label which can be added to namespaces namespaces.projectcapsule.dev/cordon trigger is true
  2. Add an Admission rule which matches these namespaces to deny any action for namespaced items. The wbehook can just straight up deny without further logic (essentially as the existing cordoning webhook
  3. Allow Owners to uncordon namespace
  4. Generate for both actions events

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions