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

Pass additional info in the mutation request to external data provider #3376

Closed
binbin-li opened this issue May 9, 2024 · 3 comments
Closed
Labels
enhancement New feature or request stale

Comments

@binbin-li
Copy link

Describe the solution you'd like
Ratify is implementing a namespaced-level multi-tenancy feature. We'd like to have both validation/mutation requests taking namespace and image to Ratify. We could easily support the validation case in the constraint template. But for mutation requests, seems we can only pass in the location value which is image in our use case since we don't actually mutate namespace. Wonder if any mutators could support users specify additional info besides the mutating fields.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Gatekeeper version: 3.15.0
  • Kubernetes version: (use kubectl version): 1.29.2
@sozercan
Copy link
Member

sozercan commented May 10, 2024

I was talking to @binbin-li offline. Sounds like ratify is storing credentials to retrieve registry info (for updating tag->digest) as secrets, the additional namespace metadata will be used for the provider to find the secret in the applicable namespace.

@maxsmythe @ritazh wdyt? does it make sense to add an "additional metadata" type of field to external data for mutation?

Copy link

stale bot commented Jul 12, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 12, 2024
@stale stale bot closed this as completed Jul 27, 2024
@JaydipGabani JaydipGabani reopened this Aug 30, 2024
@stale stale bot removed the stale label Aug 30, 2024
Copy link

stale bot commented Nov 4, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 4, 2024
@stale stale bot closed this as completed Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

3 participants