docs: document storageContainerName field for explicit CSC selection

Open Beginner friendly
#738 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Domain
documentation

Research direction

Start with docs/model-serving/storage/storage-containers.md and review the related PR #5314 for the KServe v0.20 behavior. Document the storageContainerName field, explain when explicit selection is needed versus URI-pattern matching, and add an example YAML configuration; the storage containers documentation should cover all requested guidance.

Written by the indexing model from the issue text.

Description

Summary

KServe v0.20 added a storageContainerName field to InferenceService for explicitly selecting which ClusterStorageContainer (CSC) to use for model download. No documentation exists for this feature.

What needs to be documented

  • The storageContainerName field on InferenceService spec
  • When to use it: environments with multiple ClusterStorageContainers where automatic matching may be ambiguous
  • How it differs from the default URI-pattern-based CSC matching
  • Example YAML showing explicit CSC selection
  • Update the storage containers documentation (docs/model-serving/storage/storage-containers.md)

Related PR

Since

KServe v0.20

Dominant language
MDX
Stars
113
Forks
193
Avg merge
5d 20h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kserve/website

All issues in kserve/website

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.