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

Optional strict checking mode for known GVKs in PodSet inference #150

Open
dgrove-oss opened this issue Jun 7, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@dgrove-oss
Copy link
Collaborator

dgrove-oss commented Jun 7, 2024

This is a follow on from #65.

Since we can only infer/validate PodSets for known GVKs, there may be some scenarios in which we want a strict mode where we would reject all AppWrappers that contain GVKs that aren't known to the operator.

This would mostly be for user experience and better error messages. The RBACs for the operator will prevent us from actually creating instances of unexpected GVKs, so this would just move the error from when resources are created during the Resuming phase of the AppWrapper to when the AppWrapper is initially created/validated by the WebHook.

@dgrove-oss dgrove-oss added the enhancement New feature or request label Jun 7, 2024
@dgrove-oss dgrove-oss changed the title Optional strict GVK checking mode for PodSet inference Optional strict checking mode for known GVKs in PodSet inference Jun 7, 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
Projects
None yet
Development

No branches or pull requests

1 participant