project-codeflare / project-codeflare/appwrapper
Optional strict checking mode for known GVKs in PodSet inference
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 19
- Forks
- 15
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the related issue #65 and tracing PodSet inference through the WebHook validation path and the AppWrapper Resuming phase. Define the strict-mode behavior so unknown GVKs are rejected during initial validation, with the existing RBAC behavior remaining unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100