Draft
Conversation
Co-authored-by: George Jenkins <gvjenkins@gmail.com> Signed-off-by: Scott Rigby <scott@r6by.com>
- Resolve open issues from implementation experience - Document content cache at $HELM_CACHE_HOME/content/ - Add archive-based plugin loading details - Add airgap support considerations (Open Issue helm#5) - Clean up rejected ideas section Signed-off-by: Scott Rigby <scott@r6by.com>
- Fix storage locations table (remove incorrect install cache row) - Add SDK considerations section for controller/platform use cases - Add note about gotemplate plugin handling Template built-in - Clarify helm plugin list --status=all shows separate rows - Note --from-download flag as future enhancement Signed-off-by: Scott Rigby <scott@r6by.com>
…y architecture - Remove "Chart-defined extracted" row from storage locations table - Update explanation: plugins loaded directly from tarball into memory - Update plugin loading precedence: content cache is primary path - Update --from-download example to show extraction (not symlink) - Update implementation checklist to reflect content-addressable cache The Wasm runtime (extism/v1) supports loading plugin binaries directly from bytes via CreatePluginFromData, eliminating the need for disk extraction to a versioned directory. Signed-off-by: Scott Rigby <scott@r6by.com>
- Update Plugin Storage section to clarify no fallback between installed plugins and chart-defined plugins - Add Plugin identity section explaining content hash identification - Add rejected idea helm#6: fallback to installed plugins Chart-defined plugins are identified by their SHA256 digest from Chart.lock, ensuring deterministic builds. An installed plugin with matching name/version cannot substitute because there's no way to verify the content matches the locked digest. Signed-off-by: Scott Rigby <scott@r6by.com>
Update the SDK API Requirements section to reflect the reference implementation PluginRenderer struct: - ContentCachePath (string path) instead of ContentCache interface - PreloadedPlugins as raw bytes, not pre-compiled modules - Add explicit requirements for non-writable filesystems Signed-off-by: Scott Rigby <scott@r6by.com>
Signed-off-by: George Jenkins <gvjenkins@gmail.com>
7027371 to
5f3986e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.