docs: document storageContainerName for explicit ClusterStorageContainer selection - #693
Open
RunlinXiao wants to merge 1 commit into
Open
docs: document storageContainerName for explicit ClusterStorageContainer selection#693RunlinXiao wants to merge 1 commit into
RunlinXiao wants to merge 1 commit into
Conversation
…ner selection Documents the new spec.predictor.storageContainerName field added in kserve/kserve#5314, and regenerates the CRD API reference from master. Signed-off-by: Runlin Xiao <rxiao13@asu.edu>
✅ Deploy Preview for elastic-nobel-0aef7a ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
spolti
requested review from
alexagriffith,
cjohannsen-cloudera and
sivanantha321
June 16, 2026 14:16
spolti
reviewed
Jun 17, 2026
spolti
approved these changes
Jun 18, 2026
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
2 participants
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.
Summary
Documents the new
spec.predictor.storageContainerNamefield introduced in kserve/kserve#5314 (fixes kserve/kserve#5299), which allows users to explicitly select aClusterStorageContainerinstead of relying on URI-based auto-matching when multiple CSCs support the same storage URI format.Proposed Changes
docs/model-serving/storage/storage-containers/storage-containers.mdspec.predictor.storageContainerName, with an example that selects thehf-hubClusterStorageContainer (defined earlier on the page) over thedefaultone when both supporthf://.workloadType: initContainer, and support the model'sstorageUri) and that there is no fallback to auto-matching when the field is set.LLMInferenceServicedoes not support it yet.docs/reference/crd-api.mdxmasterviamake gen-crd-api-docs(NOTES: some generation are not related to thestorageContainerName, please let me know if we wanna get them removed)Changes are made only to the
docs/("next") version since the feature ships in the next KServe release; no cherry-pick to 0.18 is needed. Verified with a fulldocusaurus build— no new broken-anchor warnings introduced by these changes.