Skip to content

What to do about dynamic creation of admission hooks and other resources? #1379

@jlewi

Description

@jlewi

Misconfigured or misbehaving webhooks are an ongoing source of problems see:

In #1213 we started adding testing to verify that webhooks are well behaved.

However, this only works if an application configures webhooks explicitly as part of its kustomize package.

We have at least two applications (katib, and kfserving) in which the webhooks are dynamically and automatically created. This has a couple disadvantages

  1. Operator doesn't know beforehand what resources will be created
  2. Operator has no way to customize the webhooks if needed
  3. Controllers need sufficient RBAC permissions to create webhooks

Should we recommend or require that all applications support at least optionally explicit creation of their webhooks and provide YAML resources to do so?

Should we enforce that by adding tests similar to #1213 to disallow RBAC permissions to create webhooks?

/cc @andreyvelich @johnugeorge @ellistarn @yuzisun @cliveseldon @animeshsingh

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions