Skip to content

research(positioning): Kubernetes admission-policy comparison #353

Description

@refeed

A document, not code: map Tirith against the in-cluster Kubernetes admission-policy engines and
their policy kinds (validate, mutate, generate, cleanup, image verification). Expected shape:
admission engines own the in-cluster moment; Tirith's axis is the change (plan, before/after,
blast radius) and multi-document correlation; mutation/generation are explicitly out of scope.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions