Skip to content

Add configuration to define namespaces for protect-webhook to manage #62

@denhamparry

Description

@denhamparry

Issue

  • Currently kube-system is hard coded to prevent kube-system pods from running in Edera Protect.
  • This isn't a hard requirement, and should be configurable.
  • We should also allow end users to determine which Kubernetes Namespaces should be managed.

Solution

  • Create a way to allow end users to either:
    • Define namespaces that protect-webhook should mutate
    • Define namespaces that protect-webhook should not mutate

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions