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

Support volume type "image" for volume mounting #15488

Open
rhuss opened this issue Sep 2, 2024 · 3 comments
Open

Support volume type "image" for volume mounting #15488

rhuss opened this issue Sep 2, 2024 · 3 comments
Labels
area/API API objects and controllers kind/feature Well-understood/specified features, ready for coding. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Issues which should be fixed (post-triage)

Comments

@rhuss
Copy link
Contributor

rhuss commented Sep 2, 2024

In what area(s)?

/area API

Describe the feature

Kubernetes 1.31 introduces a new volume type "image" which allows the direct mount of OCI container images into a Pod. According to https://knative.dev/docs/serving/services/storage/ volume mounts are supported in Knative, but the type "image" is missing.

The "image" type should be added to the allow-list for possible types so that this new K8s feature can be used.

KServe would need this for introducing such image mounts for mounting model data stored in OCI images --> kserve/kserve#3908

@rhuss rhuss added the kind/feature Well-understood/specified features, ready for coding. label Sep 2, 2024
@knative-prow knative-prow bot added the area/API API objects and controllers label Sep 2, 2024
@skonto
Copy link
Contributor

skonto commented Sep 9, 2024

As a side note we are bit behind on tested versions (1.28, 1.29) and also we are not on 1.31 from an api pov (1.30). As it is mentioned Image type was introduced in 1.31 and it is Alpha in 1.31 https://kubernetes.io/docs/concepts/storage/volumes/#image so I guess it is a bit early but we will track it.

Copy link

github-actions bot commented Dec 9, 2024

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 9, 2024
@rhuss
Copy link
Contributor Author

rhuss commented Dec 9, 2024

/remove-lifecycle stale

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 9, 2024
@skonto skonto added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Issues which should be fixed (post-triage) labels Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/API API objects and controllers kind/feature Well-understood/specified features, ready for coding. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Development

No branches or pull requests

2 participants