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

Update ROADMAP.md #519

Merged
merged 1 commit into from
Oct 8, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 6 additions & 8 deletions ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,14 +31,6 @@ As a public community project the KitOps roadmap is always open to feedback. If

* Creating a ModelKit from a Jupyter Notebook 📅

### Signing

Users can optionally sign their ModelKit using something like Cosign in order to add an extra layer of security to their packaging.

* Add docs on signing and verifying to docs 🛳️
* Decide on a signing utility 💡
* Add signing to Kit CLI 💡

### Deployment 💡

Users want to be able to deploy their models through existing CI/CD/CT pipelines. Since KitOps doesn't know the details of a user's deployment pipeline or process we will `unpack` a ModelKit into an appropriate directory structure for one of several deployment targets.
Expand All @@ -58,3 +50,9 @@ This feature will come in two parts: build attestation and self-attestation. Bui

* Add provenance for KitOps ModelKit builds 💡
* Add CLI warnings if attestation was expected and not found 💡

### Signing

Users can optionally sign their ModelKit using something like Cosign in order to add an extra layer of security to their packaging.

* Add docs on signing and verifying to docs 🛳️