Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UDS Operator Pepr policy to validate image signatures #789

Open
Racer159 opened this issue Sep 19, 2024 · 1 comment
Open

UDS Operator Pepr policy to validate image signatures #789

Racer159 opened this issue Sep 19, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@Racer159
Copy link
Contributor

Racer159 commented Sep 19, 2024

Is your feature request related to a problem? Please describe.

As Ezra I want a configurable way to enforce verification of image signatures on Pod admission to the cluster so that I can have more assurance that images come from where they say.

Describe the solution you'd like

  • Given I have a UDS Package including cosign signatures
  • And those signatures are configured to be trusted by the UDS Operator
  • When I deploy the package and a Pod is created
  • Then the UDS Operator will validate that Pod's images
  • And because they are trusted will admit them into the cluster

  • Given I have a UDS Package including cosign signatures (or not including signatures)
  • And any signatures are not configured to be trusted by the UDS Operator
  • When I deploy the package and a Pod is created
  • Then the UDS Operator will validate that Pod's images
  • And because they are not trusted will deny their admittance

Describe alternatives you've considered

We could implement checks in uds-cli and that likely makes sense to do as well long term but UDS Operator would catch it more directly where the resource is being created even if the resource did not come from UDS.

Additional context

Initially this should probably only be done for resources that we know should be controlled by UDS (i.e. have a Package CR in their namespace)

@Racer159 Racer159 added the enhancement New feature or request label Sep 19, 2024
@mjnagel
Copy link
Contributor

mjnagel commented Sep 19, 2024

This is a duplicate/very similar to #371 - maybe could consolidate any additional info into comments on that one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants